Notification of a user device to perform an action

ABSTRACT

An item-providing system supplies items to a user device for consumption at the user device via communication infrastructure. The device may correspond to a book reader device or other type of device. In one illustrative case, the item-providing system may send a notification message to the user device to notify the user device to wake up and perform one or more actions. The item-providing system may provide scheduling functionality for determining the timing at which to send the notification message.

This application claims the benefit of U.S. Provisional Application No.60/939,357 filed on May 21, 2007. This provisional Application isincorporated by reference herein in its entirety.

BACKGROUND

Users have traditionally consumed media items (such as books, magazines,newspapers, etc.) in hard-copy form. For instance, a user may obtain aphysical book from a bookstore or a library. The user may read the bookby manually flipping through its pages in conventional fashion.

A user may now also receive and consume some media items in electronicform. In one case, a user may use a personal computer to connect to anetwork-accessible source of media items via a conventional telephone orcable modem. The user may download a document from this source. The usermay consume the document by printing it out and reading it inconventional fashion. Alternatively, the user may read the document inelectronic form, that is, by reading the book as presented on a computermonitor.

A provider of electronic media items faces various challenges. Forinstance, many users continue to prefer consuming media items intraditional hard-copy form, even though these media items are availablein electronic form. The provider confronts the task of capturing theinterest of such users, while providing a viable solution from atechnical standpoint and a business-related standpoint.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows an overview of an illustrative system for downloading itemsto a user device.

FIG. 2 shows one illustrative implementation of the system of FIG. 1employing wireless communication.

FIG. 3 shows an illustrative Item Providing System (IPS) and anillustrative user device for use in the system of FIG. 2.

FIG. 4 shows a more detailed depiction of the illustrative user deviceof FIG. 3.

FIG. 5 shows an illustrative design of the user device of FIGS. 3 and 4.

FIG. 6 shows an illustrative user interface mechanism for interactingwith the user device of FIG. 5.

FIG. 7 shows a generic processing device which may be used to implementany aspect of the systems shown in FIGS. 2 and 3.

FIG. 8 is a signal diagram which depicts one illustrative manner ofoperation of the systems of FIGS. 2 and 3.

FIG. 9 shows an overview of a content reception system for use in theIPS of FIG. 3.

FIG. 10 shows an illustrative subscription module for use in the IPS ofFIG. 3.

FIG. 11 shows illustrative index-generating functionality andannotation-handling functionality for use in the IPS of FIG. 3.

FIG. 12 is a signal diagram which depicts one illustrative way toreceive and process eBooks and other pre-generated items using thecontent reception system of FIG. 9.

FIG. 13 is a signal diagram which depicts one illustrative way toreceive and process subscription-related items using the contentreception system of FIG. 9.

FIG. 14 is a signal diagram which depicts one illustrative way toreceive and process personal items using the content reception system ofFIG. 9.

FIG. 15 is a flowchart which depicts one illustrative way to receive andprocess eBooks and other pre-generated items using the content receptionsystem of FIG. 9.

FIG. 16 is a flowchart which depicts one illustrative way to receive andprocess subscription-related items using the content reception system ofFIG. 9.

FIG. 17 is a flowchart which depicts one illustrative way to receive andprocess personal items using the content reception system of FIG. 9.

FIG. 18 shows an illustrative a to-do list server module for use in theIPS of FIG. 3.

FIG. 19 is a flowchart which depicts one illustrative manner ofoperation of the to-do list server module of FIG. 18.

FIG. 20 is a flowchart which depicts one illustrative manner of managingthe to-do list server module of FIG. 18.

FIG. 21 shows an illustrative to-do list processor for use in the userdevice of FIG. 3.

FIG. 22 is a flowchart which depicts one illustrative manner ofoperation of the to-do list processing module of FIG. 21.

FIG. 23 shows an illustrative content delivery module for use in the IPSof FIG. 3.

FIG. 24 is a flowchart which depicts one illustrative manner ofoperation of the content delivery module of FIG. 23.

FIG. 25 is a flowchart which depicts one illustrative manner forprocessing items upon receipt by the user device.

FIG. 26 depicts a succession of versions, with each version differingfrom its preceding version in one or more respects.

FIG. 27 is a flowchart which depicts an illustrative delta-formingoperation performed by the content delivery module of FIG. 23 forforming a plurality of delta files.

FIG. 28 is a flowchart which depicts an illustrative server-sideincremental update operation performed by the content delivery module ofFIG. 23, utilizing the delta files generated by the procedure of FIG.27.

FIG. 29 is a flowchart which depicts an illustrative device-sideincremental update operation which complements the server-side procedureof FIG. 28.

FIG. 30 shows various content delivery management features which may beused in the systems of FIGS. 2 and 3.

FIG. 31 is a flowchart which depicts an illustrative manner of operationof reliable fulfillment processing functionality identified in FIG. 30.

FIG. 32 is a flowchart which depicts an illustrative manner of operationof late notice functionality identified in FIG. 30.

FIG. 33 is a flowchart which depicts an illustrative manner of operationof TelePhone Home (TPH) processing functionality identified in FIG. 30.

FIG. 34 is a flowchart which depicts one illustrative manner ofoperation of subscription-initiation functionality of FIG. 30.

FIG. 35 is an illustrative home page produced by a home presentationmodule shown in FIG. 4.

FIG. 36 is an illustrative menu provided in the context of the home pageshown in FIG. 35.

FIG. 37 is an illustrative set-up page accessed via the home page shownin FIG. 35.

FIG. 38 shows an illustrative merchant store module for use in the IPSof FIG. 3.

FIG. 39 shows an illustrative home page produced by the merchant storemodule of FIG. 38.

FIG. 40 shows an illustrative browsing page produced by the merchantstore module of FIG. 38.

FIG. 41 shows an illustrative item detail page produced by the merchantstore module of FIG. 38.

FIG. 42 is a flowchart which depicts an illustrative way of rescinding apurchase made with the merchant store module of FIG. 38.

FIG. 43 shows an illustrative server-side media library module and adevice-side content manager module for use in the IPS and user device,respectively, of FIG. 3.

FIG. 44 is an illustrative content manager page produced by the contentmanager module shown in FIG. 43.

FIG. 45 shows an illustrative menu provided in the context of thecontent manager page shown in FIG. 44.

FIG. 46 shows another illustrative menu provided in the context of thecontent manager page shown in FIG. 44.

FIG. 47 is a flowchart which depicts an illustrative way ofsynchronizing information between the IPS and the user device of FIG. 3.

FIG. 48 is an illustrative item-display page produced by the readermodule shown in FIGS. 2 and 3.

FIG. 49 is a flowchart which depicts an illustrative way of dynamicallypopulating a link in a page.

FIG. 50 shows an annotation-related menu presented in the context of theitem-display page of FIG. 48.

FIG. 51 is an illustrative progress bar provided in the context of theitem-display page shown in FIG. 48.

FIG. 52 shows audio delivery, management, and playback functionality ina user device as illustrated in FIGS. 3 and 4.

FIG. 53 is a modified depiction of the system of FIG. 2, emphasizing theuse of an illustrative browsing proxy module.

FIG. 54 is a flowchart which depicts an illustrative manner of operationof the browsing proxy module of FIG. 53.

FIG. 55 is an illustrative home page produced by a browser module shownin FIG. 4.

FIG. 56 shows an illustrative user interface panel for use in inputtingan address using the browser module of FIG. 4.

FIG. 57 is a modified depiction of the system of FIG. 2, emphasizingvarious administrative functions performed by the system.

FIG. 58 is a flowchart which depicts one illustrative manner ofoperation of testing functionality of FIG. 57, in which the IPSperiodically sends test probes to one or more representative userdevices.

FIG. 59 is a flowchart which depicts one illustrative manner ofoperation of upgrade-related functionality of FIG. 57, corresponding toa manual mode of upgrading.

FIG. 60 is a flowchart which depicts one illustrative manner ofoperation of the upgrade-related functionality of FIG. 57, correspondingto an automated mode of upgrading.

FIG. 61 shows an illustrative format used to forward upgrades to theuser device of FIG. 3.

FIG. 62 is a modified depiction of the system of FIG. 2, emphasizing theuse of illustrative provisioning functionality.

FIG. 63 is a flowchart which depicts one illustrative manner ofassociating item purchases to a virtual account after the purchase of anew device, but before the purchasing-user is associated with a specificuser device.

FIG. 64 shows an illustrative arrangement including test equipment and arepresentative device under test (DUT).

FIG. 65 is a flowchart which depicts one illustrative manner ofoperation of the arrangement of FIG. 64.

The same numbers are used throughout the disclosure and figures toreference like components and features. Series 100 numbers refer tofeatures originally found in FIG. 1, series 200 numbers refer tofeatures originally found in FIG. 2, series 300 numbers refer tofeatures originally found in FIG. 3, and so on.

DETAILED DESCRIPTION

According to one illustrative implementation, this disclosure sets forthfunctionality for downloading items to a user device. The functionalitymay be manifested in various systems, modules, computer readable media,data structures, methods, and other forms.

The “item” referenced above may correspond to any type of content. Inone case, the item corresponds to a digital media item. The media itemmay include, without limitation, text content, image content, audiocontent, video content, hypertext protocol content, and so on, or anycombination of these kinds of content. In addition, or alternatively,the item may include instruction-bearing content, such asmachine-readable program code, markup language content, script content,and so forth. For instance, an item may correspond to a software upgradeor the like.

More specifically, in one case, the term “item” may refer to a specificunit of merchandisable content, such as a book (e.g., an “eBook”), anissue of a magazine, and so on. Alternatively, an item may refer tosmaller parts of a merchandisable unit, such as a chapter of a book or asong in an album. Alternatively, an item may refer to a largercompilation of component items which are related in any manner. Forinstance, an item may refer to multiple issues of a magazine in aparticular year.

The term “entry” corresponds to information which refers to an item. Forexample, a list of entries may include reference information whichidentifies respective media items.

Certain drawings illustrate the features by showing various logic,modules, components, functionality, and so forth. The terms “logic,”“module,” “component,” “functionality” and the like generally representhardware, software, firmware, or any combination of these elements, oryet some other kind of implementation. For instance, in the case of asoftware implementation, the terms “logic,” “module,” “component,” or“functionality” may represent instruction-bearing content to performspecified tasks when executed on a processing unit or units (e.g., a CPUor CPUs). The instruction-bearing content may be stored in one or moremachine-readable media.

The term “machine-readable media” or the like refers to any kind ofmedia for retaining information in any form, including various kinds ofstorage devices (magnetic, optical, static, etc.). The term“machine-readable media” also encompasses transitory forms ofrepresenting information, including various hardwired and/or wirelesslinks for transmitting the information from one point to another.

Other figures illustrate features in signal diagram form and/orflowchart form. In this mode of explanation, certain operations aredescribed as constituting distinct tasks performed in a certain order.Such implementations are illustrative and non-limiting. Separateoperations described in these figures may be grouped together andperformed in a single operation, while certain single operations may beperformed in multiple parts. Certain operations may be performed in anorder different from the order illustrated in the figures. Certainoperations may be performed by different agents than is identified inthe figures. The operations shown in the figures may be implemented bysoftware, firmware, hardware, manual processing, or other form, or byany combination of these forms.

In general, the various features described in the implementations may beregarded as optional features, meaning that these features may beomitted or replaced with other features. Further, the variousimplementations described herein may be supplemented by addingadditional features.

This disclosure includes the following main sections.

-   -   Section A provides an overview of the system and its manner of        operation.    -   Section B provides additional information regarding various        components which may be used in the system of Section A.    -   Section C describes various administrative functions the system        may perform.    -   Section D describes various provisioning functions the system        may perform.

A. Overview of System and Manner of Operation

A.1. Illustrative Overview of System

FIG. 1 shows an illustrative system 100 for downloading items from anItem Providing System (IPS) 102 to a user device 104. At the device 104,the user may consume the media items in electronic form, as opposed totraditional hard-copy form. Although not shown, the user device 104represents one of a potentially great number of user devices.

As explained above, the term “item” has broad connotation. The followinglist, which is non-exhaustive, identifies representative types of items:

-   -   An item may correspond to an eBook item. An eBook item, in turn,        may refer to a book in electronic form or to one or more        portions of a book (such as a chapter of a book) or to a        compilation of multiple books (such as a book series), and so        on. An eBook is an example of a general class of items referred        to herein as pre-generated items. The term pre-generated item        refers to content typically (although not necessarily) provided        to a user in response to the user's on-demand request for the        content after it has been received and stored by the IPS 102.    -   An item of content may also correspond to a subscription-related        item. A subscription-related item refers to any item the user        receives based on a schedule or based on some other type of        pre-established arrangement. Without limitation, representative        forms of subscription-related items include magazines, journals,        newspapers, newsletters, and so on. Other forms of        subscription-related items include electronic feeds of various        types, such as Really Simple Syndication (RSS) feeds, and so on.        In contrast to a pre-generated item, a subscription-related item        is typically provided to a user in response to the receipt of        the item by the IPS 102, rather than the user's on-demand        request for a pre-generated item.    -   An item may also correspond to a personal document item, or        simply “personal item.” A personal item refers to a document the        user forwards in advance to the IPS 102, whereupon the IPS 102        converts the item to a device-readable format.    -   An item may also correspond to audio content, such as a piece of        music, a collection of music, an audio book, and so on.    -   An item may also correspond to a bundle of information generated        in response to a query made by the user.    -   An item may also correspond to instruction-bearing content, such        as a software update.    -   An item may also correspond to advertising material downloaded        to the user device by any entity or combination of entities.        Various rules may be applied to govern the downloading of this        type of item.    -   An item may also correspond to a sample of a more complete        version of the item. In one case, a sample-type item may embed        one or more links to allow the user to acquire its full-version        counterpart, or another part (e.g., chapter) of the item. In        another case, a publisher or author may release an eBook or        other item in a series of installments. Each installment may be        regarded as an item.    -   An item may correspond to a draft of an item, meaning an item in        a state that its author does not regard as necessarily final.        The term “item” may encompass yet other forms of content; the        above types of items are representative.

The item-providing system (IPS) 102 corresponds to any functionality orcombination of functionality for forwarding items to the user device104. In one case, the IPS 102 may correspond to network-accessibleserver-based functionality, various data stores, and/or other dataprocessing equipment. The IPS 102 may be implemented by a singlecollection of functionality provided at a single physical site.Alternatively, the IPS 102 may be implemented by multiple collections offunctionality, optionally provided at plural physical sites. The IPS 102may be administered by a single entity or plural entities.

In one case, the IPS 102 corresponds to an entity which provides itemsto users upon the users' purchase of the items. In this role, the IPS102 may essentially act as a bookseller or the like. In one particularcommercial environment, the IPS 102 may also offer services which allowusers to purchase hard-copy books for physical delivery to the users; inthis context, the IPS 102 may allow users to download electronic itemsto respective user devices as part of its entire suite of services. Inother cases, the IPS 102 corresponds to an entity which provides itemsto users on a non-fee basis or on the basis of some other type ofalternative compensation arrangement. Thus, the term a “provider” ofitems should be construed broadly to encompass educational institutions,governmental organizations, libraries, non-profit organizations, and soon, or some cooperative combination of any two or more entities.

The user device 104 corresponds to any type of electronic processingdevice 104 for receiving items from the IPS 102. In one implementation,the user device 104 is readily portable, meaning the user may freelycarry the user device 104 from one location to another. In oneparticular case, the user device is designed as a book reader device,also known as an eBook reader device. In this case, the user device 104functions as the electronic counterpart of a paper-based book. The usermay hold the user device 104 in a manner similar to a physical book,electronically turn the pages of the book, and so on. Withoutlimitation, FIG. 1 illustrates a particular type of eBook reader device.Additional details regarding this particular type of reader device areprovided below. Alternatively, the user device 104 may correspond to anyother type of portable device, such as a portable music player, apersonal digital assistant (PDA), a mobile telephone, a game module, alaptop computer, and so on, and/or any combination of these types ofdevices. Alternatively, or in addition, the user device 104 maycorrespond to a device which is not readily portable, such as a personalcomputer, a set-top box associated with a television, a gaming console,and so on. A communication infrastructure 106 bi-directionally couplesthe IPS 102 to the user device 104. Namely, the IPS 102 downloads items,upgrades, and/or other information to the user device 104 via thecommunication infrastructure 106. The IPS 102 receives variousinstructions and other data from the user device 104 via thecommunication infrastructure 106.

The communication infrastructure 106 may include any combination ofcommunication functionality, including any combination of hardwiredlinks and/or wireless links, etc. For instance, FIG. 2 (to be discussedbelow in turn) shows one implementation of the communicationinfrastructure 106 which includes a combination of a wide area network(WAN) and wireless infrastructure. By virtue of the wireless componentof the communication infrastructure 106, the user may use the userdevice 104 to purchase items and consume items without being tethered tothe IPS 102 via hardwired links. Thus, for instance, a user may purchaseand consume an eBook using the device while riding in a car as apassenger, while hiking in a park, while boating on a lake, and soforth.

FIG. 1 shows four exchanges which describe, in very high-level form,part of a procedure for downloading items to the user. In a firstmessage 108, the IPS 102 may send a notification message to the userdevice 104. The notification message 108 instructs the user device 104to download one or more items from the IPS 102 and/or perform otheractions. In a second message 110, the user device 104 requests the IPS102 to supply a list which identifies one or more items to be downloaded(and/or other actions to be performed, such as, in one case, sendinginformation back to the IPS 102). The user device 104 receives the listfrom the IPS 102 in response to the second message 110 (note FIG. 1 doesnot specifically identify the transmission of the list from the IPS 102to the user device 104). If the instructions identify items to bedownloaded, in a third message 112, the user device 104 sends a requestto the IPS 102, asking the IPS 102 to download the items identified inthe list. In a fourth message 114, the IPS 102 downloads the requesteditems to the user device 104. In effect, the user device 104 retrievesthe items using a pull approach, but the pull approach is initiated by apush operation (by virtue of the IPS 102 “pushing” a notificationmessage 108 to the user device 104).

In one case, the notification message 108 may correspond to a certaintype of notification message used to commence voice mode interaction,such as a telephone ring. In this case, the notification message 108 isalso referred to as a Terrestrial Phone Home or a TelePhone Home (TPH)signal. (It will be appreciated that the identifiers Terrestrial PhoneHome, TelePhone Home, TPH, etc. are arbitrary labels of convenience tofacilitate explanation herein.) The other messages may take the form ofdata mode messages. In one case, the user device 104 may be configuredto receive and act on the TPH signal without actually formally answeringthe TPH signal. In other words, the user device 104 receives the TPHsignal and does not make a voice connection, but rather initiates stepsto download items from the IPS 102. In some environments, a wirelessprovider system may charge a fee when a call is answered, but not if auser device is called and does not answer. Thus, the strategy of ringingthe user device 104 without an answer may allow the IPS 102 tocommunicate instructions to the user device 104 without incurring a feefor the user device 104 or the IPS 102.

A.2. Illustrative Wireless Implementation of the System

FIG. 2 shows a system 200 which represents one illustrativeimplementation of the general system 100 of FIG. 1. By way of overview,the system 200 includes the components identified above, namely IPS 102coupled to a user device 104 via communication infrastructure 106.

The communication infrastructure 106 includes multiple components. Afirst component is a wireless provider system 202. The wireless providersystem 202 corresponds to any infrastructure for providing a wirelessexchange 204 with the user device 104. In one case, the wirelessprovider system 202 is implemented using various data processingequipment, communication towers, and so forth (not shown).Alternatively, or in addition, the wireless provider system 202 may relyon satellite technology to exchange information with the user device104. The wireless provider system 202 may use any form ofelectromagnetic energy to transfer signals, such as, without limitation,radio-wave signals. The wireless provider system 202 may use anycommunication technology to transfer signals, such as, withoutlimitation, spread spectrum technology, implemented, for instance, usingthe Code Division Multiple Access (CDMA) protocol. The wireless providersystem 202 may be administered by a single entity or by a cooperativecombination of multiple entities.

The communication infrastructure 106 also includes acommunication-enabling system 206. One purpose of thecommunication-enabling system 206 is to serve as an intermediary inpassing information between the IPS 102 and the wireless provider system202. The communication-enabling system 210 may be implemented in anymanner, such as, without limitation, by one or more server-typecomputers, data stores, and/or other data processing equipment. Thecommunication enabling system may expose one or more ApplicationProgramming Interfaces (APIs) 208. The IPS 102 may call on the APIs 208to perform various respective functions.

The communication-enabling system 206 communicates with the wirelessprovider system 202 via a dedicated channel 210, also referred to as adedicated communication pipe or private pipe. The channel 210 isdedicated in the sense it is exclusively used to the transferinformation between the communication-enabling system 206 and thewireless provider system 202. In contrast, the communication enablingsystem 206 communicates with the IPS 102 via a non-dedicatedcommunication mechanism, such as a public Wide Area Network (WAN) 212.For example, the WAN 212 may represent the Internet.

The communication enabling system 206 may serve as an adaptor. Forinstance, assume that, in one particular implementation, the IPS 102acts as a data center which is set up to receive information via a widearea public network. Assume further the wireless provider system 202 isset up to interact with clients via a private pipe. Thecommunication-enabling system 206 interacts with the IPS 102 via thewide area network 212 and the wireless provider system 202 via theprivate pipe 210, thus accommodating the processing preferences of theIPS 102 and the wireless provider system 202. By virtue of thisintermediary role, the communication-enabling system 206 may be referredto as a Mobile Virtual Network Enabler (MVNE), while the IPS 102 may bereferred to as a Mobile Virtual Network Operator (MVNO).

In terms of a business paradigm, the IPS 102 may interact with thewireless provider system 202 using a wholesale account. On this basis,the IPS 102 may pay the wireless provider system 202 a fee based on theaggregate use of the wireless provider system 202 by all of the userdevices. The IPS 102 may recoup these costs through fees charged to theend-users. In this illustrative business scenario, the wireless providersystem 202 does not send bills directly to the users who operate theuser devices.

More specifically, the wireless provider system 102 handles an entireamount of communication traffic 214 associated with all uses of itsservices. A subset of the entire amount of communication traffic 214represents IPS-related communication traffic 216, also referred to asmerchant-related communication traffic. The IPS-related traffic 216represents the exchange of information occurring between the IPS 102 andall of the user devices which interact with the IPS 102. The wirelessprovider system 202 discriminates the IPS-related traffic 216 from othertraffic based on unique key information associated with the IPS-relatedtraffic 216. The wireless provider system 202 may prepare a bill basedon the total amount of IPS-related traffic 216. As noted above, thewireless provider system 202 may seek payment for its services from theIPS 102, not the individual users of the devices.

The examples set forth above are representative; other strategies may beused to exchange information between the IPS 102 and the user device104. In alternative cases, for instance, the system 200 may beconfigured such that the wireless provider system 202 does indeed recoupcosts directly from individual users. Or the system 200 may beconfigured such that the wireless provider system 202 submits bills toeither the IPS 102 (in aggregate) or to the individual users, at theoption of the individual respective users.

The users may access the IPS 102 through alternative communicationroutes which bypass the use the wireless provider system 202. Forinstance, as indicated by alternative access path 218, a user may use apersonal computer or the like to access the IPS 102 via the wide areanetwork 212, circumventing the wireless provider system 202 and thecommunication-enabling system 206. The user may download items throughthis route in conventional fashion. The user may then transfer the itemsfrom the personal computer to the user device 104, e.g., via a UniversalSerial Bus (USB) transfer mechanism, through the manual transfer of aportable memory device, and so on. This mode of transfer may beparticularly appropriate for large files, such as audio books and thelike. Transferring such a large amount of data in wireless fashion mayhave a relatively high cost. However, the system 200 may also beconfigured to transfer large files (such as audio files) via thewireless exchange 204. The system 200 of FIG. 2 also provides varioussecurity-related features. According to one feature, the system 200applies multiple layers of authentication. Namely, the wireless providersystem 202 includes authentication functionality A₁ 220 to perform afirst level of authentication. The communication-enabling system 206provides authentication functionality A₂ 222 to perform a second levelof authentication. The IPS 102 provides authentication functionality A₃224 to perform a third layer of authentication. Each layer ofauthentication performs checking to ensure the user device currentlyattempting to interact with the IPS 102 is duly authorized to access theIPS 102. The distributed nature of the authentication helps ensuresomeone who has obtained a user device through improper means cannotgain access to the services provided by the IPS 102.

According to another security-related feature, the system 200 mayprovide various constraints which restrict the manner in which a usermay use the device 104. For example, the communication-enabling system206 may be configured such that it will allow user devices to accessonly one or more predetermined addresses associated with the IPS 102.This means that, in one case, a user cannot use the user device 104 todirectly access a network-accessible site without being first routedthrough the IPS 102. This prevents the user from using the user device104 as an unrestricted broadband interface to network-accessibleresources.

More specifically, the IPS 102 may include a web browsing proxy (to bediscussed below in greater detail). When the user attempts to access anetwork-accessible resource 226, the communication enabling system 206first directs the user to the browsing proxy module. The browsing proxymodule may then either deny the request or accept the request byallowing the user to access the network-accessible resource 226. Thebrowsing proxy module may apply various rules (to be discussed) indetermining whether to deny or accept the request to access thenetwork-accessible resource 226. In this manner, thecommunication-enabling system 206 and the IPS 102 do not permit the userto directly access the network accessible resources.

In another case, the system 200 may allow the user to directly interactwith network-accessible resources, that is, without being routed throughthe IPS 102.

A.3. Illustrative Item-Providing System (IPS) and User Device

FIG. 3 shows a system 300 including a more detailed depiction of the IPS102 and the user device 104 (which were introduced in FIGS. 1 and 2).Although not shown, the system 300 shown in FIG. 3 may use the wirelessfeatures shown in FIG. 2. In another implementation, the system 300 mayuse some other communication infrastructure than is shown in FIG. 2,which may optionally omit the use of wireless communication.

Addressing the details of the IPS 102 first, this system 102 performsvarious functions. Different modules are associated with these differentfunctions. One module is a content reception system 302. The contentreception system 302 receives content from one or more sources ofcontent 304. The sources 304 may represent any type of provider ofcontent, such as eBook publishers, newspaper publishers, otherpublishers of periodicals, various feed sources, music sources, and soon.

The sources 304 may be administered by a single entity or may beadministered by separate respective entities. Further, the entityadministering the IPS 102 may correspond to a same entity whichadministers one or more of the sources 304. Alternatively, or inaddition, the entity administering the IPS 102 may interact with one ormore different entities administering one or more respective sources304. In the latter case, the entity administering the IPS 102 may enterinto an agreement with the source entities to receive content from thesesource entities.

In the above example, the entities associated with the sources 304 maycorrespond to commercial organizations or other types of organizations.In another case, one or more of the sources may correspond to individualusers, such as the creators of the items. For example, a user maydirectly provide items to the IPS 102. Alternatively, or in addition, auser may supply content to a community repository of items, and the IPS102 may receive content from this repository, and so on.

The content creation system 302 may obtain the content through variousmechanisms. In one case, the content reception system 302 obtains thecontent via one or more networks 306. The networks 306 may represent aWAN, such as the Internet, a Local Area Network (LAN), or somecombination thereof. The content reception system 302 may receive theinformation in various forms using any protocol or combination ofprotocols. For instance, the content reception system 302 may receivethe information by making a Hypertext Transfer Protocol (HTTP) request,by making a File Transfer Protocol (FTP) request, by receiving a feed(e.g., an RSS feed), and so forth. In another case, the IPS 102 mayobtain content via a peer-to-peer (P2P) network of sources 304. Moregenerally, the content reception system 302 may proactively request thecontent in and on-demand manner (based on a pull method of informationtransfer). Or the content reception system 302 may receive the contentin response to independent transfer operations initiated and performedby the sources 304 (based on a push method of information transfer).Alternatively, the content reception system 302 may use a combination ofpull and push transfer mechanisms to receive the content.

The content reception system 302 may receive content in the form ofitems. Without limitation, the items may include eBooks, audio books,music, magazine issues, journal issues, newspaper editions, variousfeeds, and so forth. In one case, the content reception system 302 mayreceive some items expressed in a format not readable by the user device104 (where the user device may optionally be configured to receive,process, and present content expressed in one or more predefinedformats). To address this situation, the content reception system 302may convert the items from their original format into a device-readableformat (such as, without limitation, the .mobi format).

The content reception system 302 stores the items received (andoptionally converts them to another format) in a content store 308. Thecontent store 308 includes one or more storage systems for retainingitems in electronic form, located at a single site or distributed overplural sites, administered by one or more entities.

Section B (below) provides additional information regarding theoperation of the content reception system 302. By way of preview, thecontent reception system 302 includes separate modules for handlingpre-generated items (such as eBooks), subscription-related items (suchas newspapers), and personal items (such as user-suppliedword-processing documents, etc.).

The IPS 102 also includes a subscription module 310. The subscriptionmodule 310 manages users' subscriptions to subscription-related items.Generally, a subscription entitles a user to receive one or moresubscription-related items (which are yet to be received and stored bythe content reception system 302) based on any type of consideration orcombination of considerations. Without limitation, subscription-relateditem types include magazines, journals, newsletters, newspapers, variousfeeds, and so forth. Users may arrange to receive subscription-relateditems by purchasing such subscriptions, or, more generally, byregistering to receive such subscriptions (which, in some cases, may notinvolve the payment of a fee). Alternatively, or in addition, the IPS102 may automatically register users to receive subscription-relateditems without the involvement of the users (and possibly without theapproval of the users). The latter scenario may be appropriate in thecase in which the IPS 102 (or some other entity) registers a user toreceive unsolicited advertisements, newsletters, and so on. The system300 may allow the user to opt out of receiving such unsolicitedinformation.

The IPS 102 may consult the subscription module 310 to determine whichuser devices should receive a newly-received subscription-related item.For instance, upon receiving an electronic issue of the magazine Forbes,the IPS 102 consults the subscription module 310 to determine the userswho have paid to receive this magazine. The IPS 102 then sends the issueto the appropriate user devices.

An item delivery system 312 represents the functionality which actuallyperforms the transfer of content to the user device 104. In oneillustrative representation, the item-delivery system 312 includes twocomponents: a to-do list server module 314; and a content deliverymodule 316. The to-do list server module 314 generally providesinstructions for the user device 104. The instructions direct the userdevice 104 to retrieve items and perform other operations. The contentdelivery module 316 allows the user device 104 to obtain the itemsidentified in the instructions received from the to-do list servermodule 314.

More specifically, in a first phase of information retrieval, the to-dolist server module 314 sends a notification message to the user device104. As described above, in one illustrative implementation, the to-dolist server module 314 may send the notification message as a telephonering. The user device 104 responds to the notification message by wakingup (if “asleep”), which may involve switching from a first power stateto a second power state (where the second power state consumes morepower than the first power state). The user device 104 may optionallyrespond to the notification message without formally answering thesignal, which avoids or reduces a fee associated with the wirelessmessage. The user device 104 then contacts the to-do list server module314 to request instructions from the to-do list server module 314. Morespecifically, for each user device, the to-do list server module 314maintains a list of entries, also referred to herein as a “to-do queue.”An entry provides an instruction for a user device to perform an action.As will be described in greater detail below, there are differentinstructions that a device may be directed to perform, wherein acollection of instructions defines an IPS-device interaction protocol.One such action (e.g., associated with a GET instruction of theprotocol) directs the user device 104 to retrieve an item from aspecified location, e.g., by specifying an appropriate network address(e.g., a URL) and appropriate arguments. In the first phase, the userdevice 104 generally retrieves n such entries, wherein n is an integer.In one scenario, the number n may be a subset of a total number of itemsin the to-do queue associated with the user device 104. In a secondphase of the downloading procedure, the user device 104 contacts thecontent delivery module 316 to retrieve one or more items identified inthe GET-related entries.

In general, after receiving the notification message (which may beimplemented as a telephone ring), the item delivery system 312 interactswith the user device 104 in a data mode, e.g., using the HypertextTransfer Protocol (HTTP), or some other protocol or combination ofprotocols. The downloading procedure is described in additional detailbelow (for instance, in the context of the explanation of FIG. 8).

The IPS 102 also includes a merchant store module 318. The merchantstore module 318 provides access to an item catalog 320, which, in turn,provides information regarding a plurality of items (such as eBooks,audio books, subscription-related items, and so on). As will bedescribed in greater detail below, the merchant store module 318includes functionality allowing a user to search and browse though theitem catalog 320. The merchant store module 318 may also includefunctionality allowing a user to purchase items (or, more generally,acquire items based on any terms). In one case, a user may interact withthe merchant store module 318 via the user device 104 using wirelesscommunication. Alternatively, or in addition, the user may interact withthe merchant store module 318 via another type of device 322, such as apersonal computer, optionally via wired links. In either case, when theuser purchases or otherwise acquires an item via the merchant storemodule 318, the IPS 102 may invoke the item delivery system 312 todeliver the item to the user.

The IPS 102 also includes a personal media library module 324. Thepersonal media library module 324 stores, for each user, a list of theuser's prior purchases. More specifically, in one case, the personalmedia library module 324 provides metadata information regarding eBookitems and other on-demand selections (e.g., “a la carte” selections,such as subscription issues, etc.) which a user already owns. Thepersonal media library module 324 also provides links to the items inthe content store 308. As will be described in greater detail below, todownload an eBook item (or the like) which the user has alreadypurchased, the user device 104 contacts the content delivery module 316.The content delivery module 316 interacts with permission informationand linking information in the personal media library module 324 inorder to download the item to the user. In one use scenario, the userdevice 104 may access the content delivery module 316 in this manner toinitiate downloading of an item which has been previously purchased bythe user but has been deleted by the user device 104 for any reason.

The IPS 102 also includes a browsing proxy module 326. The browsingproxy module 326 allows the user to access one or morenetwork-accessible resources 328 via a browser module (to be discussedbelow) resident on the user device 104. As explained in the context ofFIG. 2, when the user requests access to a particular network-accessibleresource, the system 300 first directs the user to the browsing proxymodule 326. The browsing proxy module 326 may then apply variousenvironment-specific business rules to determine whether or not to grantsuch access, and if granted, under what terms to grant such access.Through this mechanism, in one implementation, the user is precludedfrom directly accessing the network-accessible resources 328 using theuser device 104.

The IPS 102 also includes various security-related features, such as oneor more authorization stores 330. The authorization stores 330 provideinformation which enables various components of the IPS 102 to determinewhether to allow the user to perform various functions, such as accessthe merchant store module 318, download items, change settings, and soon.

The above-enumerated list of modules is representative and is notexhaustive of the types of functions performed by the IPS 102. Asindicated by the label “Other Server-Side Functionality,” the IPS 102may include additional functions, many of which are described below.

Now turning to the device-side features of the system 300, the userdevice 104 includes a device to-do list processing module 334. Thepurpose of the device to-do list processing module 334 is to interactwith the item delivery system 312 to download items from the itemdelivery system 312. Namely, in a first phase of the downloadingprocedure, the device to-do list processing module 334 first receives anotification message from the to-do list server module 314, whichprompts it to wake up (if “asleep”) and contact the to-do list servermodule 314 to retrieve a set of n entries. Each entry includes aninstruction which directs the device to-do list processing module 334 toperform an action. In a second phase, for a GET-type entry, the deviceto-do list processing module 334 contacts the content delivery module316 to request and retrieve an item identified by the GET-type entry. Aswill be described in greater detail below, the user device 104 signals asuccessful completion of the download process or a failure in thedownload process.

Upon downloading an item, the user device 104 stores the item in adevice-side memory 336, which in one example is a flash-type memory andmay be any other type of memory in other examples. Although not shown,the user device 104 may also exchange information with any other sourceof content 338. In one illustrative case, the other source of content338 may represent a personal computer or other data processing device.Such other source of content 338 may transfer an item to the user device104 via a Universal Serial Bus (USB) connection and/or any other type(s)of connection(s). In this scenario, the other source of content 338, inturn, may receive the item from the IPS 102 (or other source) viahardwired connection (e.g., non-wireless connection). For example, toreceive an audio book, the user may use a personal computer tonon-wirelessly download the audio book from a network-accessible sourceof such content. The user may then transfer the audio book to the userdevice 104 via USB connection. In another illustrative case, the othersource of content 338 may represent a portable memory module of anytype, such as a flash-type memory module, a magnetic memory module, anoptical memory module, and so on.

The user device 104 also includes a reader module 340. The illustrativepurpose of the reader module 340 is to present media items forconsumption by the user using the user device 104. For example, thereader module 340 may be used to display an eBook to the user to providea user experience which simulates the reading of a paper-based physicalbook.

The user device 104 also includes a content manager module 342. Thepurpose of the content manager module 342 is to allow the user to manageitems available for consumption using the user device 104. For example,the content manager module 342 allows the user to view a list of itemsavailable for consumption. The content manager module 342 alsoidentifies the sources of respective items: one such source correspondsto the device memory 336; another source corresponds to an attachedportable memory (e.g., represented by the other source 338); anothersource corresponds to items identified in the personal media librarymodule 324 (as may be revealed, in turn, by device-side metadataprovided by the IPS 102); another source corresponds tosubscription-related items identified by the subscription module 310,and so on. The content manager module 342 allows the user to filter andsort the items in various ways. For example, the user may selectivelyview items which originate from the device store 336.

The user device 104 also includes a store interaction module 344. Thestore interaction module 344 allows the user device 104 to interact withthe merchant store module 318. The user may engage the store interactionmodule 344 to search and browse through items, to purchase items, toread and author customer reviews, and so on. As described above, theuser may also use a personal computer or the like to interact with themerchant store module 318 via hardwired links.

The above-enumerated list of modules is representative and is notexhaustive of the types of functions performed by the user device 104.As indicated by the label “Other Device-Side Functionality,” the userdevice 104 may include additional functions, many of which are describedbelow. In fact, FIG. 4 shows additional device-side functionality. Forcompleteness, FIG. 4 also identifies the various modules describedabove, including the device to-do list processing module 334, the devicememory 336, the reader module 340, the content manager module 342, andthe store interaction module 344. These features perform the functionsdescribed above.

FIG. 4 shows the user device 104 also includes a browser module 402. Thebrowsing module 402 allows the user device 104 to access one or morenetwork-accessible resources 328 via the browsing proxy module 326provided by the IPS 102. As explained above, the browsing proxy module326 permits or denies access to the network-accessible resources 328based on a set of environment-specific rules. If permitted access, thedevice-side browser module 402 includes functionality for interpretingthe content received from a network-accessible source and presentingsuch content to the user.

The user device 104 may also include searching and indexingfunctionality 404. The indexing aspect of this functionality 404provides a mechanism for indexing an item received from the IPS 102and/or for interacting with an index generated and supplied by the IPS102 or by some other source. An index for a particular item (such as aneBook or newspaper edition) identifies the component parts (e.g., words)in the item, linking the component parts to their respective locationsin the item. The searching aspect of the functionality 404 provides amechanism for searching for identified components (e.g., words, phrases,etc.) in an item, and for performing other search-related functions. Thesearching aspect relies on the indexing aspect.

The user device 104 also may include an annotation module 406. Theannotation module 406 allows a user to create annotations to supplementa particular item. For instance, the user may create one type ofannotation to mark a page, thus acting in the manner of a bookmark. Theuser may create another type of annotation highlighting a portion of theitem, such as a word, phrase, sentence, etc. in an eBook. The user maycreate another type of annotation by adding one or more notes to anitem. Generally, the annotation module 406 may store annotationinformation which identifies the types of annotations created, thelocations within the item associated with the annotations, the contentof the annotations (e.g., in the case of note-type annotations), and soon.

More specifically, the user device 104 may locally store theannotations. Further, the IPS 102 may optionally store the annotationsin a backup store; this allows the user to download the annotations inthe event they are deleted from a device-side store. Wherever stored,the user device 104 may restore the annotations upon presentation of thecorresponding item which is the “target” or subject of the annotations.For example, when a user accesses an eBook which has been annotated onone or more prior occasions, the annotation module 406 may access theannotation information and display the user's annotations within thetext. The annotation module 406 may also perform a related functionallowing a user to identify and extract (e.g., “clip”) one or moreportions of an item and store such portions in a clipping file. In oneillustrative case, clippings are stored as unencrypted text files. Inone case, the annotations can be associated with a particular entity,such as a user. Alternatively, or in addition, the annotations can beassociated with a copy of the annotated item, such as an eBook.

The user device 104 also includes a home presentation module 408. Thehome presentation module 408 provides a home page when the user firstturns on the user device and/or at other junctures. The home page mayact as a general portal allowing a user to access media items andvarious features provided by the user device 104. In one illustrativecase, the home page may present a summary of some (or all) of the itemsavailable for consumption using the user device 104.

The user device 104 also includes an audio play module 410. The audioplayer module 410 provides an interface which allows the user to playback and interact with audio items, such as music, audio books and thelike.

The above-described features of the user device 104 pertains toapplications with which the user may interact or which otherwise play ahigh-level role in the user's interaction with the user device 104. Theuser device 104 may include a number of other features to performvarious lower-level tasks, possibly as background-type operations.

Power management functionality 412 performs one such background-typeoperation. More specifically, the power management functionality 412corresponds to a collection of hardware and/or software featuresoperating to manage the power consumed by the user device 104. The powermanagement functionality 412 generally operates to reduce the powerconsumed by the device 104. The power management functionality 412achieves this goal by selectively powering down features not activelybeing used (or for which there is an assumption these features are notactively being used). The power management functionality 412 achievesparticularly noteworthy power savings by powering down features whichmake large power demands, such as one or more features associated withwireless communication.

The user device 104 also includes performance Monitoring and Testing(MT) functionality 414. The MT functionality 414 maintains a performancelog 416 identifying the behavior of the device 104. The IPS 102 and/orother entities may access the performance log 416, along with otherinformation gleaned from the communication infrastructure 106, to helpdiagnose anomalies in the operation of the user device 104 and thesystem 300 as a whole. The MT functionality 414 may also interact withtesting functionality provided by the IPS 102 and/or other entities. Forexample, the MT functionality 414 may respond to test probes generatedby the IPS 102, in a manner described in further detail below in SectionC.

The user device 104 also includes an upgrade-related functionality 418.The upgrade-related functionality 418 allows the user device 104 toreceive and integrate instruction-bearing update items (such as softwareupdates). In one case, the upgrade-related functionality 418 mayautomatically receive instruction-bearing items provided by the IPS 102(and/or by other entities). An administrator at the IPS 102 may manuallyinitiate the upgrade procedure by which an instruction-bearing updateitem is forwarded to the user device 104. Or an automated IPS-sideroutine may initiate the upgrade procedure. In any event, the userdevice may receive the instruction-bearing update item without theinvolvement of the user or with minimal involvement from the user. Inthis sense, the upgrade procedure may be viewed as “transparent.” Inanother case, the upgrade-related functionality 418 may be operated bythe user to manually access a source of instruction-bearing items (suchas a prescribed website or the like) and download an item from thissource.

In one implementation, the upgrade-related functionality 418 may forwardversion information to the IPS 102. The version information identifiesthe version of the instruction-bearing content being used by the userdevice 104. The IPS 102 may determine whether this version informationis out-of-date (by reference to current version information). Ifout-of-date, the IPS 102 may react appropriately, e.g., by downloadingan instruction-bearing item to the user device 104. Section C providesadditional information regarding the operations performed by theupgrade-related functionality 418.

To repeat, the above-enumerated list of modules is representative and isnot exhaustive of the types of functions performed by the user device104. As indicated by the label “Other Device-Side Functionality,” theuser device 104 may include additional functions.

A.4. Illustrative User Interface Features

The IPS 102 described above may interact with any type of user device104. In one case, the user device 104 is a portable-type device, meaninga device designed to be readily carried from location to location. Inone specific case, the user device 104 allows the user to consume themedia items while holding the user device 104, e.g., in a manner whichsimulates the way a user might hold a physical book. A portable userdevice may take the form of an eBook reader device, a portable musicplayer, a personal digital assistant, a mobile telephone, a game module,a laptop computer, and so forth, and/or any combination of these typesof devices. Alternatively, or in addition, the user device 104 maycorrespond to a device not readily portable, such as a personalcomputer, set-top box associated with a television, gaming console, andso on.

Without limitation, FIG. 5 shows one type of user device 500 which maybe used to interact with the IPS 102. The user device 500 may include awedge-shaped body designed to fit easily in the hands of a user,generally having the size of a paperback book. Other user devices mayadopt different shapes and sizes.

In one representative design, the user device 500 includes two displayparts: a main display part 502 and a supplemental display part 504. Themain display part 502 presents various pages provided by the storeinteraction module 344, the reader module 340, the browser module 402,and so on. In one case, the supplemental display part 504 is used topresent a cursor. The user may position the cursor to identify laterallyadjacent portions in the main display part 502. Without limitation, inone illustrative case, the main display part 502 and/or the supplementaldisplay part 504 may be implemented using electronic paper technology,such as provided by E Ink Corporation of Cambridge, Mass. Thistechnology presents information using a non-volatile mechanism; usingthis technology, the user device 500 may retain information on itsdisplay even when the device is powered off.

The user device 500 includes various input keys and mechanisms. Acursor-movement mechanism 506 allows a user to move a cursor within thesupplemental display part 504. In one representative case, thecursor-movement mechanism 506 may include a cursor wheel that may berotated to move a cursor up and down within the supplemental displaypart 504. The cursor-movement mechanism 506 may be configured to allowthe user to make a selection by pressing down the wheel. Other types ofselection mechanisms may be used, such as a touch-sensitive display, aseries of vertically and/or horizontally arrayed keys along the edge(s)of the main display part 502, one or more graphical scroll bar(s) in themain display part 502, and so on.

The user device 500 also includes various page-turning buttons, such asnext page buttons (508, 510) and a previous page button 512. The nextpage buttons (508, 510) advance the user to a next page in an item(relative to a page that is currently being displayed). The previouspage 512 button advances the user to a previous page in an item(relative to a page that is currently being displayed). The user device500 may also include a page-turning input mechanism 514 actuated by theuser's thumb as it passes over the mechanism 514. This user experiencesimulates the manner in which a user turns a page in a physical book(e.g., by “thumbing through” a book). The user device 500 may alsoinclude a back button 516 allowing the user to advance to a previouspage when using the browsing module 402. Although not shown, the userdevice 500 may include a switch for turning power on and off, a switchfor enabling and disabling a wireless interface, and so on.

The user device 500 may also include a keyboard 518. The keyboard 518may include alphanumeric keys. The keys may be shaped and oriented in amanner which facilitates the user's interaction with the keys while theuser holds the device 104 in the manner of a physical book. The user mayuse the keyboard 518 to enter search terms, annotations, URLs, and soforth. The keyboard 518 may also include various special-function keys.

FIG. 6 illustrates one way in which a user may use the user device 500of FIG. 5 to select content on the main display part 502. Namely, assumethe main display part 502 displays a page of content 602. The content602 may include various selection points arrayed along its right-mostvertical edge. The selection points laterally correspond to associatedparts of the content 602. For example, a representative selection point604 corresponds to a selectable item 606 in the page of content 602. Thesupplemental display part 504 presents a cursor 608. A user may move thecursor up and down within the supplemental display part 504 by rotatingthe cursor-movement mechanism 506.

In operation, the user may operate the cursor-movement mechanism 506 sothat the cursor 608 is laterally aligned with a desired selection point,such as selection point 604 as shown in FIG. 6. In the case in which thecursor-movement mechanism 506 is a cursor wheel, the user may rotate thewheel to move the cursor 608 to a desired location along the verticalextent of the supplemental display part 504. In this implementation, theuser may then press down on the cursor wheel to formally select the item606 corresponding to the selection point 604.

Additional information regarding one representative type of book-readertype device may be found in the following family of applications:

-   U.S. Ser. No. 11/246,293, filed on Mar. 29, 2006, entitled    “Electronic Media Reader Display,” naming the inventors of    Whitehorn, et al.;-   U.S. Ser. No. 11/246,294, filed on Mar. 29, 2006, entitled    “Electronic Media Reader Keypad,” naming the inventors of Thomas J.    Hobbs, et al.;-   U.S. Ser. No. 11/246,295, filed on Mar. 29, 2006, entitled    “Wedge-Shaped Electronic Media Reader,” naming the inventors of    Whitehorn et al.;-   U.S. Ser. No. 11/277,898, filed on Mar. 29, 2006, entitled “Page    Turner For Handheld Electronic Book Reader Device,” naming the    inventors of Gregg E. Zehr, et al.;-   U.S. Ser. No. 11/277,893, filed on Mar. 29, 2006, entitled “Handheld    Electronic Book Reader Device Having Dual Displays,” naming the    inventors of Gregg E. Zehr, et al.;-   U.S. Ser. No. 11/277,873, filed on Mar. 29, 2006, entitled “Handheld    Electronic Book Reader Device Having Asymmetrical Shape,” naming the    inventors of Gregg E. Zehr, et al.; and-   U.S. Ser. No. 11/277,879, filed on Mar. 29, 2006, entitled “Keyboard    Layout for Handheld Electronic Book Reader Device,” naming the    inventors of Gregg E. Zehr, et al.

To repeat, the user interface design shown in FIGS. 5 and 6 isrepresentative. Other types of user devices having different types ofuser interface mechanisms may be used to interact with the IPS 102.

A.5. Illustrative Data Processing Device

Various aspects of the systems shown in FIGS. 1, 2, and 3 may beimplemented by one or more data processing devices. For example, variouscomponents of the IPS 102 may be implemented by respective server-typecomputers and associated data processing equipment (e.g., routers, datastorage devices, etc.). The user device 104 may also correspond to adata processing device. FIG. 7 shows an overview of a generic dataprocessing device 702 which may be used to implement any aspect of theabove-referenced systems, including any server-side features and/or anydevice-side features.

The processing device 702 includes one or more processing units 704,such as one or more CPUs. The processing device 702 also includes systemmemory 706, which may correspond to any combination of volatile and/ornon-volatile storage mechanisms. The system memory 706 may storeinformation which provides an operating system component 708, variousprogram modules 710, program data 712, and/or other components. Theprocessing device 702 performs functions by using the processing unit(s)704 to execute instructions provided by the system memory 706. Theprocessing device 702 may also include one or more types of removablestorage 714 and one or more types of non-removal storage 716.

The processing device 702 may also include one or more input devices 718(keyboard, mouse device, specialized selection keys, etc.) and one ormore output devices 720 (displays, printers, audio output mechanisms,etc.).

The processing device 702 may also include one or more communicationinterface mechanisms 722. These communication interface mechanisms 722allow the processing device 702 to interact with other processingdevices 724, such as remote computers, book reader devices, and soforth. The communication interface mechanisms 722 may include one ormore wireless interface mechanisms 726. In the case where the processingdevice 702 represents the user device 104, the wireless interfacemechanisms 726 may allow the user device 726 to receive a telephone ringand also communicate with the IPS 102 in a data mode.

The above-enumerated list of modules is representative and is notexhaustive of the types of functions performed by the processing device702. As indicated by the label “Other Device Functionality” 728, theprocessing device 702 may include additional functions.

A.6. Illustrative Manner of Downloading Items

As explained in the above sections, the item delivery system 312 of theIPS 102 interacts with the device-side to-do list processing module 334to download items from the content store 308 of the IPS 102. The itemdelivery system 312, in turn, includes two components: a to-do listserver module 314; and a content delivery module 316. The to-do listprocessing module 334 interacts with the to-do list server module 314 todownload entries, where the entries identify items to be retrieved fromthe IPS 102. The to-do list processing module 334 interacts with thecontent delivery module 316 to retrieve the actual items identified bythe entries. FIG. 8 provides additional information regarding oneprotocol 800 for downloading items from the IPS 102 to the user device104. The protocol is illustrative; it may be varied in various ways tosuit different environments.

In operation (1), the IPS's content reception system 302 receives andstores content in the content store 308. The content reception system302 may perform this operation in response to receiving a new eBook orother pre-generated item. Or the content reception system 302 mayperform this operation in response to receiving a newsubscription-related item. Or the content reception system 302 mayperform this operation in response to receiving a personal documentforwarded by the user. Still other scenarios are possible.

In operation (2), an entry is added to an appropriate queue of the to-dolist server module 314. In the case of the selection (e.g., purchase) ofan eBook, the merchant store module 318 adds an entry to the to-do listserver module 314, corresponding to an instruction to acquire theselected eBook. In this case, operation (2) occurs asynchronously withrespect to operation (1), meaning that these two operations are not partof a linked integral transaction. Although not shown in this overviewfigure, the user's purchase of an eBook (or other a la carte selection,such as a subscription issue, etc.) also prompts the IPS 102 to storeinformation regarding the user's purchase in the media library module324. In the case of the receipt of a subscription-related item, the itemreception system 302, in conjunction with the subscription module 310,add an entry to the to-do list server module 314. In this case,operation (2) occurs in response to operation (1), and thus theseoperations may be viewed as part of a single transaction. For thereceipt of a new issue of a subscription, the subscription module 310represents the user's ownership of the issue by virtue of the user'sprior purchase of the subscription, in the manner to be described ingreater detail below. In the case of a personal item, the functionalitydedicated to receiving, converting, and storing the user's personal itemmay optionally add an entry to the to-do list server module 314 (if, infact, the user has opted to receive the document via a wirelesscommunication route, instead of an alternative non-wireless mode ofdelivery).

In operation (3), the to-do list server module 314 sends a notificationmessage to the device's to-do list processing module 334. In oneillustrative case, the notification message may be implemented as atelephone ring, also referred to herein as a TelePhone Home (TPH)signal. All subsequent communication between the item delivery system312 and the to-do list processing module 334 operates in a data mode,e.g., using the HTTP protocol or some other protocol or combination ofprotocols.

In operation (4), the device's to-do list processing module 334 willwake up (if it happens to be asleep at the time) and respond to the TPHsignal. The notification process may involve switching from a firstpower state to a second power state, where the second power stateconsumes more power than the first power state. Upon waking up, theto-do list processing module 334 sends a message to the to-do listserver module 314, which requests the to-do list server module 314 toforward a list of n entries, such as, without limitation, 10 entries.The n entries may represent a subset of entries in the list maintainedby the to-do list server module 314 for the user device 104. The to-dolist server module 314 responds to this request by forwarding the listof up to n entries.

As described above, each entry provides an envelope which conveys aninstruction. One such type of instruction commands the user device 104to retrieve an item from the IPS 102. There are other types ofinstructions, which will be described in Section B. In operation (5),assuming that one or more entries of the n entries retrieved from theto-do list server module 314 correspond to GET instructions, the to-dolist processing module 334 sends a request to the content deliverymodule 316, asking this module 316 to download the items identified inthe GET instructions.

In operation (6), the content delivery module 316 responds to therequest for the items by attempting to retrieve the items from thecontent store 308. If the content delivery module 316 is successful, itforwards the requested items to the user device 104 (which may beconsidered as part of operation (5), as illustrated in FIG. 8). In somecircumstances, such as in the case of feeds, the content delivery module316 may attempt to retrieve and download a delta file which expressesthe difference between a current version of requested content and aprior version of the content, where the user device already locallypossesses the prior version. So as not to unduly complicate thisintroductory discussion, the details of the incremental updatingoperation will be provided in a later part of this description.

Operation (6) may also involve various permission-checking steps. Forexample, for the case of eBooks and other a la carte selections, thecontent delivery module 316 may consult the personal media librarymodule 324 to determine whether the user has authorization to receivethe item. In the case of subscription-related items, the contentdelivery module 316 may consult the subscription module 310 to determinewhether the user has authorization to receive the item (e.g., bydetermining whether the user is generally authorized to receive issuesof a particular subscription). So as not to unduly complicate FIG. 8,the signal flow associated with permission-checking is omitted, althoughthis detail will be provided in later figures and accompanyingdescription.

In operation (5), the content delivery module 316 may also downloadvarious hints to the user device 104. One such hint informs the userdevice 104 whether the IPS 102 stores an index corresponding to therequested item. For instance, the IPS 102 may have generated this indexwhen it initially received the item or at some other juncture. Anotherhint informs the user device 104 of whether the IPS 102 storesannotations for the requested item. These annotations may correspond toinformation created by the user and backed up by the IPS 102 on one ormore prior occasions. The user device 104 uses the hints to determinewhether it is worthwhile to even request the IPS 102 to deliver thesearch index and/or annotations for the requested item. Namely, if thecontent delivery module 316 informs the user device 104 that it does nothave a search index, then it is not a useful exercise to request theindex. The use of hints eliminates the need for the user device 104 toconduct a potentially over-the-air sluggish question-and-responseprocedure to determine whether the IPS 102 stores index informationand/or annotation information.

Assume the user device 104 is informed by the hints that the IPS 102does indeed have either (or both) a search index and backup annotations.In operation (7) the to-do list processing module 334 requests andreceives this type of supplemental information.

In operation (8), the to-do list processing module 334 stores the item(and optionally the supplemental information) in the device memory 336.

In operation (9), the to-do list processing module 334 sends a removemessage to the to-do list server module 314. This message informs theto-do list server module 314 that the user device 104 has successfullyretrieved a subset of identified items from the IPS 102 and that theto-do list server module 314 may consequently remove these items fromthe appropriate queue. In operation (10), the to-do list server module314 may acknowledge receipt of the remove message sent to it by the userdevice 104.

The retrieved n entries may correspond to only a subset of a moreencompassing list of items maintained by the to-do list server module314. If this is the case, the to-do list processing module 334 repeatsthe above-described operations by retrieving up to another n entries andreceiving the items identifies by these entries from the contentdelivery module 316.

Although not shown, upon the occurrence of an error in the downloadprocess, the user device 104 can convey error information to the IPS 102and/or vice versa.

B. Illustrative Components in System

Having set forth an overview of the system in Section A, this sectionexplains various components of the system in greater detail. While thecomponents may be used in the context of the overall system describedabove, the components may also be used in other types of systems.

B.1. Illustrative Content Reception Functionality

B.1.a. Overview of Content Reception System

As described above, the content reception system 302 receives items fromone or more sources 304 and, if appropriate, converts the items into adevice-readable format. Such conversion is also referred to as “contentcreation” herein in a liberal sense because the conversion process doesnot produce the content ex nihilo. The content reception system 302 mayinclude separate modules for handling pre-generated items (such aseBooks), subscription-related items, and personal items. Namely, thecontent reception system 302 includes an eBook processing module 902, asubscription-related processing module 904, and a user-suppliedprocessing module 906.

The eBook processing module 902 receives, processes, and stores itemsusers typically select in an on-demand manner. In one scenario, forexample, the eBook processing module 902 may receive a new eBook from apublisher source or other type of source, convert this item into adesired format, and store this item in the content store 308. Theprocessing performed by this module 902 may also involve creating asearch index for the newly received item, creating a detail page forthis item, and so on. Users may then, some time after the eBook item isstored, purchase this item, thus initiating the downloading of the itemto the user. The eBook reception process is decoupled from thedownloading process, meaning that these two operations occurasynchronously.

The subscription-related processing module 904 receives, processes, andstores items on a subscription-related basis. In one representativecase, a user may purchase a subscription which entitles the user toreceive future issues, editions, installments, etc. of asubscription-related item, such as future issues of a magazine, journal,newsletter, newspaper, blog, feed, and so forth. The reception processin this case is linked to the downloading process, meaning that thereceipt of a new subscription-related item triggers the downloading ofthis item to users who have registered to receive this item.

In a variant of the subscription-related reception operation, thesubscription-related content processing module 904 may automaticallyestablish user subscriptions and deliver items in accordance with thesesubscriptions, potentially without the involvement and/or approval ofthe users. This feature may be useful to provide advertisements tousers, to notify the users of various alerts and other events, and soon. As another example, the user may expressly purchase one or moretypes of subscriptions, and, in response, the subscription-relatedcontent processing module 904 authorizes the dissemination of theexpressly-purchased subscriptions as well as one or more othersubscriptions (which the user did not expressly purchase). In stillanother case, a user may subscribe to a single publication of an item,such as when the user pre-purchases an item which has yet to bepublished; when the item is published, the subscription-relatedprocessing module 904 will be invoked to deliver the item to the userswho have pre-purchased this item.

The user-supplied processing module 906 creates items originallysupplied by a user. In other words, in a first phase, the user-suppliedprocessing module 906 receives an item from a user. The item maycorrespond to any kind of personal document, such as a word processingdocument, a PDF document, and so on. In a second phase, theuser-supplied processing module 906 converts this item into adevice-readable format and then forwards the converted item back to theuser. The user may consume the converted item using his or her userdevice 104.

Any of the content processing modules (902, 904, 906) may rely on onemore conversion tools 908. Each conversion tool provides functionalityfor converting content from an original format into a defined targetformat. For instance, a .mobi conversion tool 910 converts content froman original format into a .mobi format. Other tools (912, . . . 914)convert an item from an original format into other respective types ofdevice-readable formats. In one case, the conversion tools 908 acceptitems in a predefined number of acceptable original formats. Withoutlimitation, in one illustrative implementation, the acceptable originalformats may include Adobe PDF format, TXT format, HTML format, rich textformat (RTF), Microsoft Word document format (DOC), and so on.Acceptable formats for images may include, without limitation, JPEGformat, GIF format, PNG format, BMP format, and so on.

B.1.b. Illustrative Subscription Module

FIG. 10 illustrates additional information regarding the subscriptionmodule 310, which was introduced in the context of FIG. 3. Thesubscription module 310 includes a subscription management module 1002.The subscription management module 1002 administers the creation andtermination of subscriptions, as well as other aspects of subscriptions.In one case, the merchant store module 318 may receive a user's purchaseof a subscription (or more generally, a user's acquisition of asubscription). The merchant store module 318 may communicate the user'sselection to the subscription management module 1002. The subscriptionmanagement module 1002, in turn, may interact with a subscription store1004, e.g., by adding new entries to the store 1004, deleting entries inthe store 1004, modifying entries in the store 1004, and so on.

More specifically, the subscription module 310 identifies subscriptionsavailable as respective parent-type nodes. When a particular issue of asubscription is received and processed, the subscription module 310associates this issue as a child node of a corresponding parentsubscription. Assume a user purchases a particular subscription; at thattime, the user is associated with a particular parent node,corresponding to the subscription. In additional, or alternatively, asubscription can be associated with a device or other entity. Further,in one implementation, the subscription module 310 manages each user'sownership of issues of this subscription by relating the user to theparent subscription, rather than individual issues of the subscription.

The subscription management module 1002 also interacts with the contentdelivery module 316 to inform the content delivery module 316 whether auser has appropriate authorization to download a subscription-relateditem (for the case of an item received as per the terms of asubscription, rather than an a la carte selection of a subscriptionitem). In one case, such permission-checking takes place on aper-subscription basis, not on a per-issue basis (unlike, in oneparticular implementation, the case of eBooks and other a la carteselections, in which permission-checking takes place on a per-itembasis).

B.1.c. Illustrative Index-Generating Functionality andAnnotation-Handling Functionality

In addition to content produced by the content reception process,supplemental information may be associated with items. One such type ofsupplemental information is index information. Another type ofsupplemental information is annotation information. FIG. 11 provides anoverview of functionality for producing such supplemental information.

As to the creation of device indexes, the IPS 102 may provideserver-side index generating functionality 1102. The server-sideindex-generating functionality 1102 may include a server-sideindex-generating module 1104 for generating an index. The server-sideindex-generating module 1104 stores the index generated in a server-sideindex store 1106. The user device 104 may include a device-side indexgenerating functionality 1108 for generating an index. Thus, both theIPS 102 and the user device 104 have the ability to generate an indexfor an item.

Various rules may be used to determine whether an index will be providedby the server-side index-generating functionality 1102 or thedevice-side index-generating functionality 1108. According to oneconsideration, the user device 104 will attempt to generate the indexusing the device-side index-generating functionality 1008, but if thisprocess proves to be too slow, the user device 104 may request theserver-side index-generating functionality to generate the index.

As to the creation and handling of annotations, the user uses adevice-side annotation generating functionality 1110 to createannotations for a particular item. (The device-side annotationgenerating functionality 1110 may be considered synonymous with theannotation module 406, introduced in FIG. 4.) The user may createbookmark-type annotations, highlight-type annotations, note-typeannotations, clipping-type content selections, and so on. The userdevice 104 may also create a “last-page-read” position. This type ofannotation identifies the last position at which an item was opened. Thedevice-side annotation-generating functionality 1110 may store theannotations in any device-side store. The user device 104 may retrieveand recreate these annotations when it displays the corresponding item.For instance, when the device reopens the item, the user device 104 mayshow the same page the user was viewing when the device 104 was closed.

The system 300 may also rely on server-side annotation-handlingfunctionality 1112 for storing a backup of the annotations created bythe user at the user device 104. The server-side annotation-handlingfunctionality 1112 may include a module 1114 of the same name forreceiving annotations from the user device 104 at various times. In onecase, the user device 104 may forward annotations to the IPS 102 as partof a cycle of operations it performs when various events occur. Suchevents may include any opportunity the device 104 has to interact withthe IPS 102 (e.g., in response to the receipt of a TPH signal, etc.).The server-side annotation handling module 1114 may store theannotations it receives from the user device 104 in a server-sideannotation backup store 1116.

If the IPS 102 stores backup annotations, it may notify the user device104 of this fact by providing hint information to the user device 104.The hint information accompanies an item forwarded from the contentdelivery module 316 to the user device. If the hint indicates thatbackup annotations are available, the user device 104 may choose todownload the annotations. The user device 104 may want to receive theseannotations in the event that the local store of these annotations hasbeen deleted, and so forth.

B.1.d. Illustrative Approach to Receiving and Processing Pre-GeneratedItems

The remainder of Section B.1 provides more information regarding theprocesses for receiving and processing eBooks and other pre-generateditems, subscription-related items, and personal items.

Starting with FIG. 12, this figure is a signal flow diagram illustratingone way to receive and process eBook items and other pre-generateditems. In operation (1), the eBook processing module 902 receives aneBook or the like from a publisher or other source. The eBook processingmodule 902 may optionally convert the eBook item to a device-readableformat, create an index for this item, and/or create a detail page whichrepresents this item in the merchant store module 318.

In operation (2), the eBook processing module 904 stores the item andits supplemental parts in the content store 308.

In operation (3), the user may operate the device-side store interactionmodule 344 to purchase or otherwise acquire the eBook from the merchantcontent store 318.

In operation (4), the eBook processing module 902 may store salientinformation in the media library module 324 which indicates the user haspurchased the eBook or other a la carte item. As will be described ingreater detail below, the content delivery module 316 may consult themedia library module 324 at the time of delivery of the item todetermine whether the user is authorized to receive the item (e.g., todetermine whether the user has actually purchased the item).

In response, in operation (5), the merchant store module 318 may add anentry corresponding to the purchased item in the user's to-do list. Thisaction prompts the to-do list server module 314 to immediately (or sometime after) send a TPH signal to the user device 104, notifying the userdevice 104 that an instruction is outstanding to acquire an item.

The top half of the signal diagram corresponds to a creation phase 1202of the operation, in which a new eBook is received and processed. Thebottom half of the signal diagram corresponds to a delivery phase 1204of the operation, in which a user purchases and receives a previouslystored item. The creation phase 1202 precedes the delivery phase 1204but these two phases (1202, 1204) are not otherwise linked together.

FIG. 15 shows a procedure 1500 which describes the eBook processingoperation in flowchart form.

In block 1502, the eBook processing module 902 receives a new item,e.g., from a publisher of items or some other source.

In block 1504, the eBook processing module 902 optionally converts thenew item into a device-readable format—that is, assuming the item is notalready expressed in a device-readable format.

In block 1506, the eBook processing module 902 optionally creates anindex for the item, an item detail page, and/or other supplementalinformation associated with the item.

In block 1508, the eBook processing module 902 stores the converted itemand any supplemental information associated with the item.

In block 1510, at any time later, the merchant store module 318 receivesthe user's purchase of the item.

In block 1512, the eBook processing module 902 stores purchaseinformation in the media library module 324. This information identifiesthe user has purchased a particular eBook or the like.

In block 1514, the merchant store module 318 or some other server-sidemodule adds an entry to the device's to-do queue in the to-do listserver module 314. This entry contains an instruction which instructsthe user device 104 to retrieve the purchased item.

Block 1516 generally references an item delivery procedure, which isinvoked to download the item. Later figures describe this operation ingreater detail.

B.1.e. Illustrative Approach to Receiving and ProcessingSubscription-Related Items

FIG. 13 is a signal flow diagram illustrating one way to receive andprocess subscription-related items. In operation (1), thesubscription-related processing module 904 receives and processes asubscription-related item. This processing may involve converting theitem into a device-readable format, indexing the item, and so forth.

In operation (2), the subscription-related processing module 904 storesthe received subscription-related item in the IPS content store 308.Although not shown in FIG. 15, in the subscription module 310, the newissue is identified as a child node of a corresponding parentsubscription. As explained above, in one case, permission-checking atthe time of delivery proceeds on a general subscription-level basis,rather than on a per-item (e.g., per-issue) basis. However, if the userhas made a separate selection of a subscription-related item (e.g., an ala carte selection), then the above-described eBook permission-checkingis used to govern access to the item.

In operation (3), the subscription-related processing module 904consults the subscription module 310 to determine the users who shouldreceive the newly received subscription-related item.

In operation (4), the subscription-related processing module 904 maystore an entry in each of the to-do queues of the identified subscribingusers.

FIG. 16 shows a procedure 1600 which describes the subscription-relatedprocessing operation in flowchart form.

In block 1602, the subscription-related processing module 904 receives anew subscription-related item, such as a magazine issue, a newspaperedition, a feed item, and so on.

In block 1604, the subscription-related processing module 904 convertsthe received item into a device-readable format if appropriate, andoptionally produces supplemental information, such as a device index.

In block 1606, the subscription-related processing module 904 stores thereceived (and potentially converted) subscription-related item in thecontent store 308.

In block 1608, the subscription-related processing module 904 consultsthe subscription module 310 to determine the users who should receivethe subscription-related item.

In block 1610, the subscription-related processing module 904 providesan entry in each of the to-do queues of the users who will be receivingthe subscription-related item.

Block 1612 generally references an item delivery procedure, which isinvoked to download the item. Later figures describe this operation ingreater detail.

B.1.f. Illustrative Approach to Receiving and Processing PersonalDocuments

FIG. 14 is a signal flow diagram illustrating one way to receive andprocess personal items (such as a personal document). In operation (1),the user uses Email functionality or other message-generatingfunctionality to forward a personal item to the user-supplied processingmodule 906. For instance, the user may include the personal item as anattachment to an Email message. In one case, the user may forward asingle personal item with the Email message. In another case, the usermay forward multiple personal items with the Email message, e.g., asmultiple attachments to the Email message. The user-supplied processingmodule 906 allows the user to bundle together one or more attachments,e.g., in a ZIP file or the other form of package.

In one implementation, the user-supplied processing module 906 isconfigured such that it will only accept an Email message from the userfrom one or more pre-authorized Email addresses. In one case, the useris allowed to select the Email address(es) in a configuration procedure(e.g., via one or more configuration user interface pages), therebyestablishing a permitted list of Email addresses. The user-suppliedprocessing module 906 may initially provide a default Email addresswhich may be used by the user; the user may later change or supplementthis default Email address. Placing restrictions on the permissibleEmail addresses is potentially useful to eliminate or reduce the amountof unwanted items forwarded to the user. Unwanted items may beparticularly pernicious in the case in which the user is charged anover-the-air delivery fee to receive these items. However, in anotherimplementation, the user-supplied processing module 906 may not placeany restrictions on the Email addresses that may be used to forwardpersonal items to the user-supplied processing module 906.

In operation (2), the user-supplied processing module 906 may receiveand process the received message (in the event that the messageoriginates from an address identified on the permitted address list).Such processing may involve interpreting the message to identify thesource of the message, the target destination that the converted item(s)will be sent to, and/or other salient information regarding the message.The processing also involves extracting the personal item(s) from themessage and converting the item to a device-readable format. In the casethat one or more personal items are packaged in a ZIP file or the like,the extracting operation may involve removing one or more personal itemsfrom this package file.

The above-described processing operation may wholly succeed, whollyfail, or partially succeed (and partially fail). A partial failure mayoccur when the Email message contains multiple personal items asattachments, and the user-supplied processing module 906 is successfulin converting some of these items but not others. For instance, theunsuccessfully converted items may be expressed in an unsupportedoriginal format. In operation (3), the user-supplied processing module906 may notify the Email sender of any type of failure (either totalfailure or partial failure). In the case of a partial failure, theuser-supplied processing module 906 may continue processing thesuccessfully-processed item(s), e.g., by delivering these items to theUser.

The user may select at least two delivery options to receive theconverted personal item(s). In a first option, the user may request thatthe converted personal item(s) be forward to the user in wireless form.If this is the case, in operation (4), the user-supplied processingmodule 906 adds an entry to the user's to-do queue in the to-do listserver module 314. In a second option, the user may request that theconverted personal item(s) be made available to the user via anon-wireless route. For example, the user may request that the converteditem(s) be sent to the user in an Email form. The user may extract theconverted personal item(s) from the Email message and then transfer theconverted personal item(s) to the user device 104 via hardwired link,such as via USB connection. Or the user may request that the converteditem(s) be posted to a network-accessible site. The user may access thissite using a personal computer or like mechanism, download the converteditem(s) (over non-wireless infrastructure), and then transfer theconverted item(s) to the user device via USB connection or othermechanism. Operation (5) generally represents the delivery of one ormore personal items via a non-wireless route. A user may generallyprefer to the use the non-wireless route to avoid the possible expenseof downloading content over the air.

FIG. 17 shows a procedure 1700 which describes the personal itemprocessing operation in flowchart form.

In block 1702, the user-supplied processing module 906 receives amessage from the user, such as an Email message, which includes anattached user-supplied item (or plural items).

In block 1704, the user-supplied processing module 906 determineswhether the message originates from a permissible address by consultingthe permitted address list. If so permitted, the user-suppliedprocessing module 906 parses and interprets the message, as well asextracts the personal item(s) attached thereto. Extracting the items mayinvolve removing the items from a package file of any kind.

In block 1706, the user-supplied processing module 906 converts thepersonal item(s) to a device-readable format, if, in fact, the personalitem(s) is (are) not currently in such a format. The user-suppliedprocessing module 906 can rely on a single mechanism to perform thisconversion; alternatively, the user-supplied processing module 906 canrely on any one or more of multiple available conversion mechanisms. Forinstance, the user-supplied processing module 906 can select aconversion mechanism that it deems to be the most suitable forconverting a particular type of item; in addition, or alternatively, auser may forward instructions that identify one or more mechanisms to beapplied to a particular item. In one case, if the user-suppliedprocessing module 906 is not successful in processing the item using onetype of conversion mechanism, it can try another conversion mechanism,and so on.

In addition, or alternatively, conversion may optionally involveresizing the personal item into a form that better accommodatespresentation of the converted item by a user device. That is, thisprovision may make the converted item more readable when presented onthe device.

In addition, or alternatively, conversion may involve rotating thepersonal item, e.g., by 90 degrees, to again better accommodatepresentation of the converted item by the user device.

In addition, or alternatively, conversion may involve breaking up thepersonal item into multiple parts for presentation on the user device inmultiple pages. For example, as shown to the rights of block 1706, theuser-supplied processing module 906 may rotate the personal item by 90degrees and then break it up into multiple parts. This operation may beappropriate for certain personal items that have large images (forexample, PDF documents with scanned page images). Again, this provisionmay make the converted item more readable when presented on the device.

In block 1708, the user-supplied processing module 906 determines whatroute the user wishes to use to receive the converted personal item(s).In one case, the determination performed in block 1708 may be implied.For instance, the user-supplied processing module 906 may provide afirst Email address for receiving items that are to be sent over awireless route once converted. The user-supplied processing module 906may provide a second Email address for receiving items that are to besent over a non-wireless route. If the user sends the personal item(s)to the first Email address, then it is understood that the user wishesto receive the converted item via a wireless route. If the user sendsthe personal item(s) to the second Email address, then it is understoodthat the user wishes to receive the converted item(s) via a non-wirelessroute. In another case, the user-supplied processing module 906 mayprovide a single Email address for receiving personal items. Theuser-supplied processing module 906 may discriminate the selecteddelivery route by interpreting instructions provided in the messageitself, and so on.

Assume that the user has selected a wireless delivery route. In thiscase, in block 1710, the user-supplied processing module 906 adds anentry to the user's to-do queue in the to-do list server module 314.

Block 1712 generally references an item delivery procedure, which isinvoked to download the item(s). Later figures describe this operationin greater detail.

Next assume that the user has selected a non-wireless delivery route. Inblock 1714, the user-supplied processing module 906 makes the converteditem(s) available to the user through an alternative transfer mechanism,such as Emailing the converted item(s) back to the user, posting theconverted item to a network-accessible site, and so on.

As indicated in block 1716, the user-supplied processing module 906 mayascertain whether there are any failures in the processing of theitem(s). If so, in block 1718, the user-supplied processing module 906sends an error notification message to the sender. If there is only apartial failure, then processing proceeds with respect to the item(s)that may be successfully processed.

B.2. Illustrative to-do Server Module

This section provides additional information regarding an illustrativecomposition and operation of the to-do list server module 314. Recallthat the to-do list server module 314 operates by sending instructionsto the user device 104, thereby instructing the user device 104 toretrieve items and perform other actions. The to-do server module 314includes a to-do list receiving module 1802. The to-do list receivingmodule 1802 receive entries from various sources, such as the variousprocessing modules (902, 904, 906) described in the previous section.For instance, the to-do list entry receiving module 1802 may receive anentry when a user purchases an eBook or like content, when asubscription-related item is received, when the user sends a personaldocument to the IPS 102, and so on. All of these events cause thegeneration of a GET-type entry, which serves as an instruction for theuser device 104 to download the item corresponding to the GET-typeentry. Other IPS-side modules may add a GET-type entry to a queue tonotify the user device 104 that it should download an item that providesan instruction-bearing upgrade. Other types of entries may conveydifferent types of instructions. In one case, an entity within the IPS102 may generate a delete (DEL) instruction which instructs the userdevice 104 to delete an item that it may have previously received andstored in its device memory 336. In one circumstance, the user may havepurchased an item, which prompted the generation of a GET-type entry.But later it may be determined that the user's credit standing isdeficient, precluding the purchase of the item. In this case, anappropriate entity in the IPS 102 (such as the merchant store module318) may add a DEL-type entry to the user's to-do queue.

In another case, an appropriate entity in the IPS 102 (such asmonitoring and/or testing functionality) may add a command (e.g., a PUTinstruction) to a user's to-do queue to request the user device 104 toforward performance logs and/or other information to the monitoringand/or testing functionality.

In another case, an appropriate entity in the IPS 102 may addinformation to the to-do queue which prompts the user device 104, uponreceipt of this entry, to display information to the user, e.g., in apop-up form or other type of alert-related form.

The IPS 102 may add yet additional types of instructions to the users'to-do queues to suit different applications and environments. The to-dolist server module 314 may include to-do list stores 1804 formaintaining a plurality of to-do lists, also referred to as to-doqueues. More specifically, the to-do list server module 314 may maintaindifferent queues for respective user devices, such as a to-do list A foruser device A, a to-do B for user device B, and so on. A user deviceinteracts with its own respective to-do list, as represented by thedashed-line box in FIG. 18, which indicates that the entries in mailboxstore A are designated for user device A.

The to-do server module 314 also includes a device interaction module1806. The purpose of the device interaction module 1806 is to allow theto-do server module 314 to interact with the device-side to-do listprocessing module 334. The device interaction module 1806 includes anotification module 1808. The notification module 1808 forwards anotification message to user device 108, e.g., in the form of aring-type TPH signal. The device interaction module 1806 thereafterinteracts with the user device 104 in a data mode. Namely, the deviceinteraction module 1806 receives the user device's request for a list ofn entries in the user's to-do queue, upon which the device interactionmodule 1806 provides this list. The device interaction module 1806 maylater receive the user device's instruction to remove one or moreentries from the list, indicating that the user device successfullydownloaded the items associated with the those entries.

The to-do list server module 314 includes a to-do list management module1810. The to-do list management module 1810 manages entries posted to auser's to-do queue. In one case, an entity may post a GET-type entry toa user's queue, and then the same entity or another entity may post aDEL-type entry, instructing the user device 104 to delete the same itemthat the device was previously asked it to get. In this circumstance, inone case, the to-do list management module 1810 may delete the GET-typeentry, but not the DEL-type entry. This action may be appropriate in ascenario in which the user device 104 has already received the GET-typeentry and may be in the process of downloading the corresponding item.

In another case, the to-do list management module 1810 determines that auser's to-do queue contains several editions of a newspaper or otherperiodical. The to-do list management module 1810 may remove all but themost current edition of the periodical, under the premise that a userwill not want to read an old newspaper. The user may be given the optionof making set-up selections which override this behavior. In anothercase, the user may access older editions of a newspaper via the contentmanager module 342, in a manner to be discussed below.

In general, the to-do list management module 1810 helps ensure that theto-do list queue does not contain inconsistent or redundant entries, orsome other undesirable entry-type content.

FIG. 19 shows a procedure 1900 which illustrates one manner of operationof the to-do server module 314 in flowchart form. The procedure 1900 isexplained with reference to the delivery of items to a particular userdevice; the to-do server module 314 uses the same procedure to forwarditems to other user devices.

In block 1902, the to-do server module 314 receives one or more to-doentries. This action may be triggered by the purchase of new eBooks andthe like, the receipt of new subscription-related items, and do on.

In block 1904, the to-do server module 314 stores the entries in anappropriate mailbox (where such a mailbox is associated with the userdevice that will eventually receive the items).

In block 1906, the to-do server module 314 sends a TPH signal to theuser device to alert the user device to the presence of one or moreentries that it may download. More specifically, in one implementation,TPH scheduling functionality may receive TPH events. Based on one ormore considerations, the TPH scheduling functionality may decide whetherto immediately send a TPH signal or to delay sending the TPH signal(e.g., by possibly coalescing plural TPH events and sending a single TPHsignal). Additional details regarding the TPH scheduling functionalityare provided in below. The TPH scheduling functionality may beimplemented as a feature of the notification module 1808.

In block 1908, the to-do server module 314 provides n entries to theuser device, in response to the user device requesting these items.

In block 1910, after the user device has successfully performed theactions identified by the entries (such as downloaded one or more items,deleted one or more items, and so on), then the user device 104 sends aremove instruction to the to-do server module 314. In operation 1910,the to-do server module 314 responds to this request by removing theentries of the to-do queue.

FIG. 20 shows a procedure 2000 which illustrates one manner of operationof the to-do list management module (“management module”) 1810 of theto-do list server module 314. In one implementation, the procedure of2000 is performed when a new entry is added to a to-do queue, e.g.,between operations 1902 and 1904 of FIG. 19.

In block 2002, the management module 1810 analyzes the entries in theto-do queue (along with the candidate entry that is to be added to theto-do queue). More specifically, the management module 1810 mayspecifically examine entries currently stored in the queue waiting to besent to the user device. The management module 1810 may also considerentries that have already been forwarded to the user device 104.

In block 2004, the management module 1810 identifies any two or moreentries that may conflict with each other for any reason, or which maycause any other concern. One example of a conflict is the case in whicha GET-type entry contradicts a DEL-type entry for the same item. Anotherexample of an actionable issue is where a to-do queue contains severaleditions for a same newspaper or other periodical. Another example of anactionable issue is where a to-do queue contains exact duplicateentries, and so on.

In block 2006, the management module 1810 takes steps to resolve ormitigate any problems caused by conflicting entries, if possible.Operation 2004 may entail making modifications to the queue, such asdeleting one or more entries to the queue, adding one or more entries tothe queue, and so on. Operation 2004 may additionally, or in thealternative, involve sending corrective commands to the user device.

B.3. Illustrative To-Do List Processing Module

FIG. 21 shows details of the device-side to-do list processing module334. The modules shown in FIG. 21 complement many of the modules shownin FIG. 18 for the to-do list server module 314.

The to-do list processing module 334 includes a TPH-receiving module2102 for receiving a notification message from the IPS 102, e.g., in theform of a telephone ring. The TPH receiving module 2102 may act on theTPH signal without formally answering this signal, after which the to-dolist processing module 334 exchanges information with the IPS 102 usinga data mode. Upon receiving the TPH signal, the user device 104 maytransition from a first power state to a second power state, where thesecond power state consumes more power than the second power state. Thisis assuming that the user device is not already in the second powerstate.

The to-do list processing module 334 includes a list server interactionmodule 2104 for use in handling all interaction with the to-do listserver module 314 (except the TPH aspects of this interaction). Namely,the list server interaction module 2104 may send a request to receive alist of n entries from the to-do list server module 314, and thenreceive such list if the retrieval operation is successful. After theuser device obtains the items referenced by the entries in the list(and/or performs other actions identified by the entries), the listserver interaction module 2104 may send a remove instruction to theto-do list-server module 314, instructing the to-do list server module314 to remove corresponding items from its to-do queue.

The to-do list processing module 334 includes a content delivery (CD)interaction module 2106. The purpose of the CD interaction module 2106is to interact with the server-side content delivery module 316 torequest and obtain items that are identified in the list of n entries.The CD interaction module 2106 may also receive various hints from thecontent delivery module 316, as well as supplemental information (e.g.,index information, backup annotations, etc.). The CD interaction module2106 may store items and other information that it receives in thedevice memory 336 or in some other storage medium (or media).

The to-do list processing module 314 may also include a device-sidemanagement module 2108. This device management module 2108 coordinatesthe operation of the to-do list processing module 334. The devicemanagement module 2108, in turn, may include a device-side incrementalupdate module 2110 and a device-side error handling module 2112. Theincremental update module 2110 and error handing module 2112 work incooperation to govern the retrieval operations performed by the CDinteraction module 2106. The incremental update operation is describedin detail in a later section.

By way of preview, if appropriate for a particular type of item beingrequested (having a prescribed content), the incremental update module2110 may instruct the CD interaction module 2106 to obtain an identifieditem by first requesting a delta file. The delta file expresses thedifference between a device-side version of the desired content and acurrent version of the content. If this operation is not successful forany reason (as assessed by the error handling module 2112), theincremental update module 2110 may instruct the CD interaction module2106 to request a full version of the identified item. As will bedescribed, the content delivery module 316 of the IPS 102 includes aserver-side incremental update module which handles the incrementalupdate operation in an independent but complementary manner to thedevice-side incremental update module 2110.

FIG. 22 shows a procedure 2200 which describes the operation of thedevice to-do list processing module 334 in flowchart form.

In block 2202, TPH receiving module 2102 receives a notification messagefrom the to-do list server module 314, optionally in the form of atelephone ring. The download process may also be initiated by otherevents. For example, the process may be initiated in response to theactivation of a “Check New Items” command (e.g., made available via oneor more device menus). The process may also be initiated by turning onthe user device 104 radio (from an off state). The process may also beinitiated when the user device 104 enters a geographical location wherewireless service is available from a location where it was notavailable, and so on.

In block 2204, in response to the notification message, the user devicetransitions to an appropriate power state (if not already in theappropriate state). The list server interaction module 2104 thenrequests and receives n entries from the to-do queue maintained by theto-do list server module 314.

In block 2206, the CD interaction module 2106 requests items identifiedby the n entries.

In block 2208, the CD interaction module 2106 receives the items (if thedownload is successful), together with hints. A first hint notifies theuser device 104 an index for an item is available at the IPS 102. Asecond hint notifies the user device 104 backup annotations areavailable at the IPS 102. The first and second hints may also be used toindicate an index and/or backup annotation are respectively notavailable.

In block 2210, the CD interaction module 2106 optionally downloadssupplemental information (if deemed appropriate). Such additionalinformation comprises search index information and annotationinformation.

In block 2212, the CD interaction module 2106 stores the retrieveditem(s) and supplemental information in the device memory 336 and/or insome other storage location(s).

In block 2214, the list server interaction module 2104 notifies theto-do list server module 314 that it has successfully downloaded theitems, allowing the to-do list server module 314 to remove thecorresponding entries from the to-do queue.

FIG. 22 shows that operations 2206-2214 may be performed in en blocfashion, e.g., by effectively downloading multiple items and performingother actions as an integral process. In another implementation, afterreceiving the list of n entries in block 2204, the user device 104 mayperform operations 2206-2214 for the first entry in the list, followedby performing operations 2206-2214 for the second entry in the list, andso on, until the user device 104 processes all of the n entries.

B.4. Illustrative Content Delivery Module

B.4.a. Overview of the Content Delivery Module

FIG. 23 provides additional details regarding the server-side contentdelivery module 316. The server-side content delivery module 316performs a host of functions relating, in part, to the delivery of itemsto the user device 104 upon its request.

To begin with, the content delivery module 316 includes a downloadmodule 2302. The download module 2302 coordinates with the CDinteraction module 2106, receiving requests for items from this module2106, and, if possible, delivering the requested items to the CDinteraction module 2106. The download module 2302 retrieves therequested items from the content store 308. The download module 2302also may retrieve supplemental information from the index store 1106 andthe annotation store 1116. The index store 1106 stores an index (ifavailable) for an item being requested. The annotation store 1116 storesbackup annotations (if available) for an item being requested.

The download module 2302 may include an incremental download module2304, which retrieves delta information from a delta information store2306. The purpose of the download module 2302 is to download, ifpossible, a delta version of requested content, rather than the fullversion of the requested content. A delta version of requested contentcorresponds to the difference between a device-side version of therequested content and a current version of the requested content. Morespecifically, the delta information store 2306 provides various deltafiles, each file corresponding to a difference between a potentialdevice-side version of requested content and the current version of therequested content (where what is regarded as the current version changeswith the reception of each new version). In general, the download module2302 attempts to forward a delta version of the requested content(selected from a collection of delta files in the delta informationstore 2306), rather than the entire content, to reduce the amount ofinformation that is transmitted from the IPS 102 to the user device 104.So as not to unduly complicate the discussion of FIG. 23, the details ofthe incremental update process will be provided at a later portion ofexplanation.

A number of modules of the content delivery module 316 support thedownload module 2302 in various respective capacities. For example, thecontent delivery module 316 includes a hint-providing module 2308. Thehint-providing module 2308 prepares and forwards a hint which identifieswhether an index exists in the index store 1106 for a particularrequested item. The hint-providing module 2308 also prepares andforwards a hint which identifies whether backup annotations exist in theannotations store 1116 for a particular request item. Each hint may beexpressed as a Boolean Yes-No type of field, or in some other format.The hint-providing module 2308 may send the hints along with the itemsprovided by the download module 2302.

The content delivery module 316 also includes an annotation formattingmodule 2310. The annotation store 116 may store the backup annotationsin a generic form in annotation store 1116. Assuming that backupannotations are available and the user device 104 requests theseannotations, the annotation formatting module 2310 may convert thebackup annotations from its generic form to a form which is compatiblewith the format of the corresponding item itself, such as the format ofthe eBook item itself. The download module 2302 may then forward theannotations to the user device in a desired format.

In one implementation, the annotation store 116 fully describes alltypes of annotations identified above. In another illustrativeimplementation, the annotation store 1116 only stores the locations ofthe annotations and the content of user notes. In this case, theannotation store 1116 may not store actual excerpts associated withhighlight-type and clipping-type annotations. In one implementation, theannotation formatting module 2310 may contact the content store 308 torequest excerpts based on the stored locations of the annotations. Thisallows the system to reconstruct highlight-type and clipping-typeannotations.

The content delivery module 316 also includes an encryption module 2312.The encryption module 2312 may optionally encrypt an item to bedelivered to the user device 104 for a particular user. This maycomprise receiving an item from the content store 308 and applyingDigital Rights Management (DRM) and/or other protection-relatedprocessing to a header of the item. The encryption module 2312 need notstore an entire copy of the item in memory before applyingencryption-related processing to the item. In other words, theencryption module 2312 may stream out the item to the user device 104,applying encryption to parts of the item as appropriate. In one case,the encryption module 2312 applies encryption to all items that itdelivers. In another case, the encryption module 2312 applies encryptionto some items (such as eBooks, subscription-related items, etc.) but notother items (such as personal items and IPS-generated messages, etc.).

The content delivery module 316 also includes a personalization module2314. The personalization module 2314 may insert personalizedinformation into an item prior to its being delivered to a user. Forexample, the item may include one or more placeholder fields. Thepersonalization module 2314 may populate the placeholder fields withpersonalized information, such as the name of the user, and so forth.

The content delivery module 316 also includes a metadata injectionmodule 2316. As the name suggests, the metadata injection module 2316inserts metadata into the item before it is delivered to the user. Themetadata may include the names of the authors of the item. As will bediscussed, the content manager module 342 may display this nameinformation to the user in one or more user interface pages. Themetadata may also include information that specifies the location wherethe text of the item starts. This location information enables a “go tothe beginning” feature that may be invoked via one or more menusprovided by the user device 104. The metadata may also include a customtitle for the item. This metadata allows the content delivery module 316to present an item with a personalized message, such as “Thank You,John,” in one or more pages, and so on. The last-mentioned featureoverlaps with the role of the personalization module 2314 describedabove.

The metadata injected into the item may also include item identificationinformation, such as a unique ID number used by the merchant storemodule 318 to identify the item. More specifically, in one illustrativeimplementation, when the content reception system 302 receives andprocesses content, it does not couple an ID number with the item itselfin the content store 308. The content reception system 302 stores IDinformation elsewhere in the IPS 102. At time of delivery of aparticular item, the metadata injection module 2316 may associate theitem with its ID number and send out this combination of information asa package. For instance, the metadata injection module 2316 may insertID information in the header of the item prior to delivery.

In one case, the encryption module 2312 and the metadata injectionmodule 2316 (and/or other modules) may operate in series as discreteoperations. In another case, the encryption module 2312 and the metadatainjection module 2316 (and/or other modules) may operate generally as asingle integrated operation.

The content delivery module 316 also includes an authorization module2318. The authorization module 2318 determines whether the user isentitled to receive the item(s) being requested. The authorizationmodule 2318 may make reference to one more fields of authorizationinformation to makes its decision, such as information which indicateswhether a user has suitably paid for the content being requested. Asexplained above, for an eBook item and other a la carte selections, theauthorization module 2318 may interact with the media library module 324to determine whether the user has purchased (or is otherwise dulyentitled to receive) the item. For a subscription-related item that isprovided as per a subscription, the authorization module 2318 mayinteract with the subscription module 310 to determine whether the useris generally authorized to receive issues of a particular subscription(e.g., without making a per-item authorization inquiry).

The content delivery module 316 also includes a download restrictionmodule 2320. The download restriction module 2320 may be implemented aspart of the authorization module 2318 or a separate module. The downloadrestriction model 2320 may optionally restrict the downloading of anitem to a maximum number of devices, such as, in one illustrative case,five devices.

The above-enumerated list of modules is representative and is notexhaustive of the types of functions performed by the content deliverymodule 316. As indicated by the label “Other Modules” 2322, the contentdelivery module 316 may perform additional operations. Further, in someimplementations, the content delivery module 316 may omit one or more ofthe modules identified in FIG. 23.

FIG. 24 shows a procedure 2400 which explains one illustrative manner ofoperation of the content delivery module 316 in flowchart form. Theorder of operations illustrated in FIG. 24 may be modified in variousways. Further, one or more blocks shown in FIG. 24 may be omitted.Further, one or more operations may be performed at the same time; inthis case, FIG. 24 illustrates these functions as distinct operations tofacilitate explanation of these functions.

In block 2402, the content delivery module 316 receives a request fromthe to-do list processing module 334 for one or more items. Tofacilitate discussion, the flowchart will assume that the user device104 has requested a single item.

In block 2404, the content delivery module 316 performs variousauthorization-related operations, e.g., as described above with respectto the authorization module 2318 and the download restriction module2320.

In block 2406, the content delivery module 316 retrieves the identifieditem from the server content store 308.

In block 2408, the content delivery module 316 may optionallypersonalize the item, such as by inserting the user's name in aplaceholder field in the item.

In block 2410, the content delivery module 316 may assign anidentification number to the item and/or inject other metadata into theitem.

In block 2412, the content delivery module 316 may optionally encryptthe header of each item that it delivers for a particular user. Asexplained above, the content delivery module 316 may apply encryption toan item without requiring that the entire item be stored in memory.

In block 2414, the content delivery module 316 may forward the prepareditem to the user device 104. The items may be accompanied by hints whichrespectively describe whether the IPS 102 maintains an index for theitem and backup annotations for the item.

In block 2416, the content delivery module 316 may receive a request forsupplemental information, such as a request for a server-side indexand/or a request for backup annotations.

In block 2418, the content delivery module 316 may forward the requestedsupplemental information to the user device 104.

In block 2410 the process assigns an identifier to the item, and mayinject other metadata.

FIG. 25 shows an illustrative procedure 2500 which explains one mannerin which the user device 104 may process an item upon receipt.

In block 2502, the user device 104 receives a requested item. The itemcorresponds to a specific type of content, which may be an eBook item, asubscription-related item, a bundle of answers to a user's query, and soon. The item may also be represented by one or more identificationnumbers, also known as keys. In one case, each edition or issue of asubscription-related item is assigned a unique identification number.

In block 2504, the user device 104 determines whether the type and key(e.g. the identification number) of the item are the same as an itemthat is currently stored by the user device 104. If so, for eBook itemsand subscription-related items, this means that the user device is nowreceiving a completely redundant copy of an item which it alreadypossesses. In the case of feeds, this may mean that the user device 104is receiving at least a new version of the feed, which may add and/oromit one or more parts with respect to a previous version of the feed. Aversion identifier may be used to identify the version of a receivedfeed.

In block 2506, if the item is deemed redundant, the user device 104 mayconsolidate the newly received item with the previously stored itemhaving the same type and key, thereby only creating a single record forthis entry.

In block 2508, if the item is not deemed to be redundant, the userdevice may store the newly received item as a distinct new item. In oneimplementation, at this juncture, the user device 104 may also check thereceived hints and download the appropriate supplemental information(annotation backup information, and/or index information, etc.).

B.4.b. Illustrative Approach to Incremental Updating

FIGS. 26-29 describe a procedure for performing incremental updating.The general purpose of this procedure is to provide the user device witha delta version of requested item, rather than the full version of therequested item, if possible. A delta version of a requested itemexpresses the difference between a version of the content that isalready possessed by the device (e.g., a “device version”) and a currentversion of the content. Upon receipt of the delta version, the deviceconstructs the full version of the requested item by integrating (e.g.,patching) the delta version of the item into the existing prior (device)version. The procedure attempts to provide a delta version of therequested item to the user device 104 to help reduce the amount ofinformation being transmitted from the IPS 102 to the user device 104,and the cost associated therewith (particularly with regard to wirelesscommunication costs).

The incremental update operation takes place on both the IPS 102 and theuser device 104. These two operations occur independently of each other,but these operations also complement each other. FIGS. 27 and 28describe the incremental update procedure from the standpoint of the IPS102, while FIG. 29 describes the incremental update operation from thestandpoint of the user device 104.

Starting with FIG. 26, this figure shows an overview of one scenario inwhich it may be appropriate to perform an incremental update. In thiscase, the user has subscribed to receive a feed. A feed corresponds to acollection of informational parts which are supplied to the user atpredetermined times (e.g., hourly) or in response to other triggeringevents. Consider, for example, the case of a feed which providesheadline news stories. Such a feed may forward a list of the top tennews stories every hour. If a collection at time n has prescribedreference content, then a collection at time n+1 may be viewed as alater “version” of the content at time n.

One version of a feed may contain one or more parts that are shared incommon with an immediately prior version of the feed. In the case of anews feed, the top ten news stories at 2:00 PM on a particular day mayinclude many of the same news stories identified at 1:00 PM. And perhapsall of the news stories may be the same. In this circumstance, it isdesirable to download only the delta version of 2:00 PM news feed. Thedelta version of the news feed identifies only those parts of the 2:00PM news feed which are different than the 1:00 PM news feed. A currentversion of content may differ from a prior version of the content in atleast two respects. First, a current version of the content may add oneor more parts that are not present in a prior version of the content.Second, a current version of the content may, in addition oralternatively, remove one or more parts that are present in a priorversion of the content.

FIG. 26 represents an evolution in a sequence of content, from versionV₁ to version V₄. Version V₄ represents a current version of the contentat a most current point in time. In version V₁, the content includesbase part A₁ and supplemental part A₂. In version V₂, the contentincludes base part A₁ and supplemental parts A₂ and A₃. In version V₃,the content includes base part A₁ and supplemental parts A₂, A₃, and A₄.Finally, in version V₄, the content includes base part A₁ andsupplemental part A₃ and A₄, yet now omits part A₂ which was present inversion V₃.

The illustrative strategy adopted by one implementation of theincremental update procedure is to compile, in advance, delta fileswhich express the difference between the current version (e.g., V₄) andeach prior version. For instance a first delta file expresses thedifference between version V₄ and version V₃. This delta file consistsof simply an indication that part A₂ has been removed. A second deltafile expresses the difference between version V₄ and version V₂. Thisdelta file consists of an instruction that part A₂ has been removed,together with the information contained in part A₄ (which has beenadded, relative to version V₂). A third delta file expresses thedifference between version V₄ and V₁. This delta file consists of aninstruction that part A₂ has been removed, together with the informationcorresponding to parts A₃ and A₄ (which were added, relative to versionV₁). In the delta files, the parts that have been omitted need not bereproduced; a reference to the omitted parts will suffice.

In an application phase of the incremental update procedure, the contentdelivery module 316 determines the identity of the item that the user isrequesting and determines whether the user has a prior version of therequested content, such as version V₃, version V₂, version V₁, etc.Without limitation, in one case, the user device 104 may inform thecontent delivery module 316 of the version of the content that itpossesses (if any) in header information included in the requests thatit sends to the IPS 102. The content delivery module 316 first makes anattempt to access the delta file which expresses the difference betweenthe current version of the requested content and the device version ofthe requested content. If this delta file may be obtained, and if it isdetermined that it is more efficient to send the delta file as opposedto the whole file, then the content delivery module 316 sends the deltafile, rather than the entire requested item. Else, the content deliverymodule 316 sends the entire requested item. As mentioned, the userdevice 104 performs a parallel analysis, first requesting a delta file.If the user device 104 does not receive and successfully process thedelta file in due course, it may ask for a full version of the requesteditem.

FIGS. 27-29 formalize the above explanation in flowchart form. Startingwith FIG. 27, this figure illustrates a procedure 2700 for forming deltafiles. This operation may be performed by the IPS's content deliverymodule 316 as a background process, and, in particular, by theincremental update module 2304 shown in FIG. 23.

In block 2702, the content delivery module 316 makes note of the receiptof a new version of content, such as a new edition of a feed, a newedition of a newspaper item, and so on.

In block 2704, the content delivery module 316 forms a series of deltafiles, expressing the difference between the current version V_(n) and aseries of prior versions, V_(n-1), V_(n-2), V_(n-3), and so forth. Thecontent delivery module 316 may apply various rules to determine howmany delta files it should compute. In one case, the delivery module 316may cap the number of delta files at a predetermined number. Recall thatthe objective is to download a requested item to the user in the mostefficient manner. As such, in another case, the delivery module 316 maystop forming delta files when it determines that the delta file becomesso large and/or complex that it may be more efficient to download theentire item rather than a delta file. The content delivery module 316may store the delta files in a delta file store 2306 (shown in FIG. 23).The delta files may be stored with their corresponding full items orotherwise linked to their corresponding full items by referenceinformation.

In block 2706, the content delivery module 316 may remove any deltafiles from a previous iteration that are no longer relevant. Forinstance, in a previous iteration of the procedure, the version V_(n-1)was the most current version of the item, and all of the delta fileswere compiled with reference to this version. In one implementation, thecontent delivery module 316 may delete all of these stale delta files,based on the presumption that the user will want the most currentversion of the requested item.

FIG. 28 shows a procedure 2800 which represents the application phase ofthe incremental update procedure, in which a user device makes aspecific request for an item, corresponding to requested content. Theincremental update module 2394 of the content delivery module 316 may beused to perform the procedure 2800.

In block 2802, the content delivery module 316 receives a request for anitem. The content delivery module 316 may determine whether the userdevice 104 has a prior version V_(k) of the requested content throughvarious mechanisms, such as by reading the version information from aheader of the user device's HTTP requests.

In block 2804, the content delivery module 316 attempts to access adelta file corresponding to the difference between the current versionV_(n) and the device's version V_(k). In one case, the content deliverymodule 316 may make n attempts to access this delta file, such as,without limitation, 3 attempts.

If the content delivery module 316 is successful in accessing the deltafile (as determined in block 2806), it may provide the delta file inlieu of the full version. Namely, in block 2810, the content deliverymodule 316 sends the delta file as opposed to the full item. Otherwise,in block 2812, the content delivery module 316 sends the entire item.

The above-described manner of operation is based on the assumption thatthe delta-forming procedure 2700 of FIG. 27 is operative to store deltafiles for only those cases in which it deems it more efficient totransmit a delta file, rather than the entire version. In this case, ifprocedure 2800 does not find a corresponding delta file, it proceeds byimmediately accessing and downloading the full version. In other cases,the determination of whether it is more efficient to send the delta fileas opposed to the entire version may be performed as part of thedownload process of FIG. 28, e.g., as indicated by the optional decisionblock 2808. Regardless of what juncture the delta-vs-full decision ismade, this decision may be based on a number of factors:

-   -   First, the size of the delta file relative to the entire item is        relevant. If the delta file is larger than the entire item, then        it makes no sense to transmit the delta file in lieu of the        entire item. In this case, the content delivery module 316 will        decide to transmit the entire file.    -   Second, the decision process may take into consideration the        fact that the entire item may be better compressed (and/or        encrypted) compared to the delta file. Thus, in determining        relative size, the decision process may examine the compressed        size of the delta file relative to the compressed size of the        entire item.    -   Third, there is a finite amount of item required to patch the        delta file into a pre-existing version at the user device, and        to perform other operations that are uniquely associated with        processing the delta file (as opposed to the entire item). The        decision process may choose to take these time lag        considerations into account when deciding whether it is more        efficient to transmit the delta file as opposed to the entire        item.

FIG. 29 shows a procedure 2900 which sets forth a complementaryincremental update operation performed by the user device 104. Theincremental update module 2110 and error handling module 2112 of FIG. 21may be used to perform this procedure 2900.

In block 2902, the user device 104, as a default rule, attempts toaccess a delta file version of a requested item. If successful, the userdevice 104 attempts to patch the delta file into the version of thecontent that it currently possesses. The user device 104 may optionalmake a predetermined number n of attempts to perform this operation.

In block 2904, the user device 104 determines whether or not it issuccessful in obtaining the requested item as a delta file patch. If itis successful, the process ends. If it is not successful, in block 2906,the user device 104 may request the entire item. The user device 106 mayapply other considerations (rather than, or in addition to,success/failure-type considerations) in determining whether to downloada delta file or a full item.

To repeat, the server-side content delivery module 316 may perform itsincremental updating operation (as per procedure 2800) in parallel withthe user device 104, which performs its own incremental updatingoperation (as per procedure 2900). Either the IPS 102 or the user device104 may decide to abandon its attempts to retrieve the delta fileversion of the requested item.

B.5. Delivery Management Functionality

B.5.a. Overview of the Delivery Management Functionality

In the examples developed above, the IPS 102 operates by receiving anitem, adding an entry to an appropriate to-do queue (in the case of asubscription-related item), and then sending out a TPH signal to notifythe user device to access the entry and subsequently download thecorresponding item. This section describes various management functionsdesigned to make this general process more efficient and/or to achieveother goals.

FIG. 30 shows a collection of content delivery management features 3000.A first feature corresponds to reliable fulfillment functionality 3002.The reliable fulfillment functionality 3002 operates by performingdelivery-related processing in advance of the point in time at which anitem is ready to be delivered to a user device. Such prefatoryprocessing may comprise adding an entry to the device's to-do queueprior to the point in time at which the item is ready to be delivered.

A second feature corresponds to TPH scheduling functionality 3004. TheTPH scheduling functionality 3004 generally attempts to schedule thetransmission of TPH signals to reduce the power consumed by the userdevice 104. More specifically, it is relatively expensive (from thestandpoint of the consumption of power) for a user device wake up andact on a TPH signal (e.g., by receiving entries from a to-do queue anddownloading items, etc.). In one representative case, such an eventconsumes about 1 percent of the total capacity of the battery life. Toaddress this situation, the TPH scheduling functionality 3004 may notsend a TPH signal for every reportable addition made to the to-do queue,but rather, combine multiple reportable events together and send out asingle TPH signal. The TPH scheduling functionality 3004 applies otherconsiderations in determining when and how to send out TPH signals, aswill be described in greater detail below. In one implementation, theTPH scheduling functionality 3004 may be implemented as a feature of thenotification module 1808.

A third feature corresponds to late notice functionality 3006, alsoknown as paperboy functionality. The late notice functionality 3006determines that a publisher is late in providing a subscription-relateditem to the IPS 102. In response, the late notice functionality 3006 mayidentify all of the recipients of the item. The late noticefunctionality 3006 may prepare and send out personalized late notices tothe recipients.

A fourth feature corresponds to subscription initiation functionality3008. The subscription initiation functionality refrains from startingthe subscription until the user first turns on the device and contactsthe IPS 102. This provision may apply to both fee-based and freesubscriptions.

The above-enumerated list of features is representative and is notexhaustive of the types of functions performed by the IPS 102. Asindicated by the label “Other Coordination Functionality” 3010, the IPS102 may include additional management features. The IPS 102 may alsoomit or disable one or more of the features shown in FIG. 30.

The following subsections describe each of the features in greaterdetail.

B.5.b. Illustrative Reliable Fulfillment Functionality

FIG. 31 is a flowchart which shows a procedure 3100 for implementing thereliable fulfillment functionality 3002, introduced above.

In block 3102, the reliable fulfillment functionality 3002 receives atriggering event which commences the reliable fulfillment processing.The event may correspond to the receipt of a subscription-related item,and so on.

In block 3104, the reliable fulfillment functionality 3002 performsprefatory processing in preparation for sending out a TPH signal to oneor more devices which are registered to receive the item. In one case,the reliable fulfillment functionality 3002 may store an entry in theto-do queue associated with a device which is scheduled to receive theitem. At the time that the reliable fulfillment functionality 3002 addsthe entry to the to-do queue, the content reception module 302 may beconverting the item, so that, at this time, the item is not yet ready tobe forwarded to the user device. To prevent the to-do list server module314 from prematurely sending out a TPH signal upon adding an entry to aqueue, the entry may be tagged with a flag which identifies it as notready to be sent. This mechanism may also optionally effectively concealthe entry from the list of entries that the device sees when it requestsentries as part of the download process (e.g., in block 2204 of FIG.22).

In block 3106, the reliable fulfillment functionality 3002 allows theTPH signal to be sent to the recipient device when the item is ready tobe sent. In the case of the above-described subscription-related item,the reliable fulfillment functionality 3002 determines when the contentreception system 302 is finished converting the content and storing itin the content store 308. At this time, the reliable fulfillmentfunctionality 3002 may change the status of the entry in the to-do queueto indicate that a TPH signal may be sent to the user device.

The reliable fulfillment functionality 3002 may perform other types ofprefatory actions. In general, the prefatory actions expedite thedelivery of items, as these operations may be performed in parallel withother operations and/or when the parts of the IPS 102 are otherwise idleor not fully engaged.

B.5.c. Illustrative Late Notice Functionality

FIG. 31 is a flowchart which shows a procedure 3200 for implementing thelate notice functionality 3006, introduced above. The procedure 3200 isdescribed with respect to a particular subscription-related item, butthe procedure 3200 may be repeated in aggregate for a collection ofsubscription-related items and/or other types of items.

In block 3202, the late notice functionality 3006 determines that apublisher or other source is late in providing a subscription-relateditem to the IPS 102. Or the late notice functionality 3006 may determinethat there is some other source of delay with respect to an item. Thelate notice functionality 3006 may make this determination based oninformation regarding when an item is normally received. Suchinformation may be expressed by manually-entered timing information. Ifthe late notice functionality 3006 determines that a predeterminedamount of time has elapsed beyond the expected receipt of the item, thenit may identify the item as being late. The late notice functionality3006 may glean information regarding the expected receipt of an itemfrom various sources, such as from the administrators of the IPS 102,from the publisher itself, and so on. Alternatively, or in addition, thelate notice functionality 3006 may compile empirical norms which reflectthe typical timing at which the item is received and processed. Inmaking lateness determinations, the late notice functionality 3006 maytake into consideration the time zones in which user devices receivecontent. For example, a first late threshold may apply to a user who isoperating his user device on the East Coast of the United States, whilea second late threshold may apply to a user who is operating his deviceon the West Coast. The difference in thresholds may account for the factthat there may be less time to react to a delayed delivery on the Eastcoast compared to the West coast. More specifically, assume that anewspaper normally arrives at 4:00 AM, East Coast time. A delay indelivery is more of a concern for East Coast users than West Coast usersbecause the East Coast users will be waking before the West Coast usersand expecting to receive their newspapers with breakfast.

In block 3204, assuming that it is determined that an item is late, thelate notice functionality 3006 may send out a late notice to each userwho is scheduled to receive this item. The late notice functionality3006 may consult the subscription module 310 to determine the set ofusers who are scheduled to receive the item. The late noticefunctionality may optionally personalize the late notices provided tousers, such as by inserting the users' names into placeholder fields ina generic late notice message. The late notice message may also becustomized to identify the name of the late publication, the date of thelate issue, and so on.

In block 3206, the late notice functionality 3006 sends out the latenotices to appropriate users. The late notice functionality 3006 maytake into consideration the respective time zones of subscribers bysending out late notices at appropriate times.

In one case, the late notice functionality 3006 may send the latenotices as documents, e.g., like any other type of items describedabove. The late notice functionality 3006 may deliver the late noticesby adding GET-type entries in appropriate to-do queues. In anotherimplementation, the late notice functionality 3006 may send specialcommands in the to-do queues. These commands prompt the user devices,upon receipt of the commands, to display an appropriate pop-up messageor the like, informing the users that the items will be delivered late.The late delivery module 3006 may optionally send a staggered series oflate messages upon continued failure to deliver the item, with eachmessage including an appropriate escalation of apologies, remedies, andthe like.

In block 3208, when (and if) the late issue is delivered, the latenotice functionality 3006 may remove the late notice item from the userdevices (e.g., by sending a DEL-type command to the user devices viacorresponding to-do queues). This provision gives the IPS 102 anopportunity to avoid confusion for a user who opens her device to seeboth a delivered item and a notification that the item is late.

B.5.d. Illustrative Telephone Home (TPH) Functionality

FIG. 33 is a flowchart which shows a procedure 3300 for implementing theTPH scheduling functionality 3004, introduced above. Recall that oneillustrative goal of the TPH scheduling functionality 3004 is toschedule TPH signals to reduce the number of times that a user deviceneeds to power on, receive the TPH signals, and download entries anditems. The TPH scheduling functionality 3004 achieves this result, inpart, by aggregating multiple TPH signals into a single TPH signal basedon various rules, and/or by adjusting the timing when TPH signals aresent out. The procedure 3300 will be described with respect to anillustrative to-do queue associated with a particular user device,although the operations set forth here may be performed for a pluralityof to-do queues and associated user devices. In one implementation, theTPH scheduling functionality 3004 may be implemented as a feature of thenotification module 1808.

In block 3302, it is assumed that a user's to-do queue contains at leastone entry. If so, in block 3302, the TPH scheduling functionality 3004determines whether it is appropriate to send a TPH signal to the userdevice, or to defer such a message until some time later. The to-do listserver module 314 may refrain from sending a TPH signal for an entry ina to-do queue by flagging this entry with a non-send status. The statusmay be changed when the to-do list server module 304 wishes to send outthe TPH signal.

In making its decision, the TPH scheduling functionality 3004 may relyon any one of the following considerations or any combination of thefollowing considerations. Many of the considerations include aspectswhich intersect with other considerations.

-   -   The TPH scheduling functionality 3004 may consider one or more        time-related factors in deciding when to send a TPH signal, such        as time-of-day information. For instance, the TPH scheduling        functionality 3004 may be more willing to send a TPH signal        during the daytime hours rather than at night if it is likely        that the user is already using the device 104 during the day; in        this case, sending the TPH signal may not cause the device to        power up, since the device may already be powered up. On the        other hand, the TPH scheduling functionality may be more willing        to send a TPH signal during the night rather than the day if        there is a significant cost savings to conducting wireless        communication at night, rather than during the day. In another        application of time-related considerations, the TPH scheduling        functionality 3004 may be configured to send a single TPH signal        every t interval of time, such as every half hour, every hour,        and so on (providing that at least one TPH-sending event has        been registered in the interval t).    -   The TPH scheduling functionality 3004 may consider the type of        item as significant in determining when to send a TPH item. For        instance, a user who expressly purchases an eBook is likely to        be relatively interested in receiving this item soon after his        or her purchase, since the user made an express request for the        item, and furthermore, this express action is a recent event. On        the other hand, a recipient of a journal or blog may be less        concerned with receiving an issue immediately after it becomes        available, as there is less compelling evidence that the user        remains actively interested in this material. As such, the TPH        scheduling functionality 302 may send a TPH item for the eBook        soon after the user makes a purchase. But the TPH scheduling        functionality 3004 may delay sending the TPH signal upon the        automated reception of a subscription-related item. More        generally stated, the TPH scheduling functionality 3004 may        assign different priorities to item types. The TPH scheduling        functionality 3004 may then consider the priority of the items        in a to-do queue as one factor in determining how quickly to        send out a TPH signal. To cite another example, upgrade        functionality at the IPS 102 may add an entry to a device's        to-do queue that instructs the device to download an        instruction-bearing update. This entry may be earmarked as a        very high priority item, demanding that a TPH signal be sent        immediately.    -   The TPH scheduling functionality 3004 may also consider the        length of time that an entry has been stored in a to-do queue in        determining when to send a TPH signal. The TPH scheduling        functionality 3004 may not wish to delay sending out a TPH        signal for too great an amount of time.    -   The TPH scheduling functionality 3004 may also consider the        prior behavior exhibited by the user in determining whether to        download a TPH signal. More specifically, in one case, the TPH        scheduling functionality 3304 may consider the aggregate        behavior of many users, based on the presumption that this        behavior may likewise apply to a particular user. In another        case, the TPH scheduling functionality may alternatively, or in        addition, consider the unique behavior of a particular user. To        cite one example, a particular user may have unique patterns of        behavior, such that the user operates her user device at one        time of day but not another. The TPH scheduling functionality        3004 may also identify patterns in the types of actions that the        user typically performs in the course of a day. Based on these        considerations, the TPH scheduling functionality 3004 may send a        TPH signal during a time at which the user is expected to be        already using the device, and thus operating the device in a        powered-up state. According to another example, users generally,        considered in aggregate, may wish to receive certain types of        content at certain times of day. For instance, users may wish to        read newspapers before leaving for work. In this case, the TPH        scheduling functionality 3004 may attempt to send THPs prior to        5:00 AM, but the TPH scheduling functionality 3004 need not        otherwise send TPH signals throughout the night while the users        are presumed to be sleeping.    -   The TPH scheduling functionality 3004 may also collect        information regarding a user's current use of the device 104.        For instance, the TPH scheduling functionality 3004 may        determine the user has plugged the user device 106 into a        permanent power source (such as an AC power outlet or the like).        The TPH scheduling functionality 3004 is more apt to send a TPH        signal to the user device if it may be determined that a user        has plugged the device 104 into a non-exhaustible source of        power. The TPH scheduling functionality 3004 may also receive        information which reveals the battery level of the user device        104. The TPH scheduling functionality 3004 may be more reluctant        to send a TPH signal if the battery state of the device is low.    -   The TPH scheduling functionality 3004 may also consider the        amount of entries stored in the to-do queue. The TPH scheduling        functionality 3004 may be more apt to send a TPH signal if the        user's to-do queue is becoming full with unreported entries. The        TPH scheduling functionality 3004 may also consider a recent        rate of TPH-sending behavior.    -   The TPH scheduling functionality 3004 may also consider the        express preferences of a user, e.g., as entered by a user via a        setting-type page or the like.    -   The TPH scheduling functionality 3004 may also identify, for a        subscription-related item, whether the user has just purchased        the item. A user who has just purchased an item may be more        eager to receive an issue of this item, as opposed to a user who        has been regularly receiving issues for an extended period of        time.    -   The TPH scheduling functionality 3004 may also consider the size        of the item to be downloaded in determining the timing at which        to send a TPH signal. For example, the TPH scheduling        functionality 3004 may opt to send a TPH signal for a        particularly large item at night, such as to incur smaller        over-the-air download-related fees.    -   Still other considerations may have a bearing on the TPH        scheduling decision made by the TPH scheduling functionality        3004. As a related point, note that the user device 104 may be        configured such that it independently contacts the to-do server        module 314 in response to various events (e.g., without being        prompted to do so by a TPH signal), such as when the device        powers up for any reason, and so forth. The user device may then        download any entries in its queue that may be pending at that        time.

In block 3304, the TPH scheduling functionality 3004 weights one or moreof the above-identified factors in making a final decision whether ornot to send a TPH signal. Different environments may apply differentweights to these considerations, influencing which consideration maytake precedence over other considerations. In one case, each user mayalso define the weights that apply to the sending of TPH signals,thereby controlling the relative importance of the various factorsidentified above.

In block 3306, the TPH scheduling functionality 3004 sends out a TPHsignal, prompting the user device to retrieve the entries and downloadthe corresponding items associated with the entries.

B.5.e. Illustrative Subscription Initiation Functionality

FIG. 34 is a flowchart which shows a procedure 3400 for implementing thesubscription initiation functionality 3008, introduced above.

In block 3402, the subscription initiation functionality 3008 determinesthat the user has purchased a new subscription.

In block 3404, the subscription initiation functionality 3008 delayscharging the user for issues or editions of the subscription until theuser actually begins downloading subscription-related items, or inresponse to some other consumption trigger. This measure is, in part, acourtesy to the user.

B.6. Illustrative Home Presentation Module

The home presentation module 408 introduced in the context of FIG. 4provides a home page through which a user may begin interacting with theuser device 104. The home presentation module 408 may present a varietyof information on the home page. FIG. 35 provides one illustrativeimplementation of a home page 3502.

The home page 3502 of FIG. 35 shows a list of various items that a usermay consume using the reading device, including eBooks, audio books,personal items, subscription-related items, and so forth. Each entry inthe home page 3502 includes the salient information regarding the item,such as the title of the item, the author of an eBook-type item, and soforth. Each entry includes a selector (along the right edge of the page3502) that serves as a guide for selecting the corresponding item,thereby opening the item for viewing. A special grouping type selector3504 indicates that the item corresponds to a subscription. By clickingon this item, the user may view a list of available issues within thesubscription. Further, each entry in the home page includes a progressindicator, such as progress indicator 3506. The number of dots in theprogress indicator 3506 identifies how far the user has advanced inreading the item, relative to a total length of the indicator.

The home page 3502 also includes a “Show and Sort” selection item. Byclicking on this entry, the user may receive a Show and Sort menu (notshown). This menu allows the user to select a filtering criterion (orcriteria) that is (or are) used to select items for presentation in thehome page 3502. The user may also select a sorting criterion (orcriteria) that is (or are) used to govern the order in which items aredisplayed on the home page 3502.

The home page 3502 also includes a menu selector 3502. Selecting themenu selector 3502 prompts the user device 104 to present the menu 3602shown in FIG. 36. The menu 3602 allows the user to navigate to variousfunctions performed by the user device and perform specialized tasks.One such function that may be selected via the menu 3602 is a settingoption 3604.

By activating the setting option 3604 shown in FIG. 36, the user device104 directs the user to a settings page 3702, shown in FIG. 37. Thesettings page allows the user to change various administrative settingsassociated with the device (such as account name, device name, etc.), aswell as change various settings that govern the manner of operation ofthe device. The settings page 3702 also reveals the amount of storageavailable to store additional items.

B.7. Illustrative Merchant Store Module

B.7.a. Overview of the Merchant Store Module

FIG. 38 shows the merchant store module 318, introduced in the contextof FIG. 3. By way of overview, the merchant store module 318 allows theuser to search for items, purchase (or otherwise acquire) selecteditems, and so forth. The user interacts with the merchant store module318 via a store interaction module 344 provided by the user device 104.The user may also interact with the merchant store module 318 via one ormore alternative mechanisms, such as by using a personal computer whichaccesses the merchant store module 318 via a non-wireless communicationmechanism (e.g., telephone or cable modem, DSL mechanism, etc.).

The merchant store module 318 includes an account administration andset-up module 3802. This module 3802 allows the user to set up a useraccount and perform other administrative functions.

The merchant store module 318 also includes or has access to userinformation 3804. The user information 3804 may provide demographicinformation regarding the users. The user information 3804 may alsoprovide information regarding the prior purchases and other types ofselections made by the users. The merchant store module 318 may includean item catalog 320. The item catalog 320 may include descriptions ofvarious items that may be selected using the merchant store module 318.A description of an item in the item catalog 320 may take the form of anitem detail page.

The merchant store module 318 may include Item Review and Acquisition(IRA) functionality 3806. The IRA functionality 3806, in turn, mayinclude a catalog search and presentation module 3808; this module 3808allows the user to review items in the item catalog 320 by enteringsearch terms, viewing browse categories, and so on. The IRAfunctionality 3806 also includes an item recommendation module 3810. TheIRA functionality 3806 presents one or more recommended items to theuser, e.g., based on the user's prior interests (e.g., as reflected inthe user information store 3804), or based on generally popular items,and so on.

The IRA functionality 3806 also may include an item purchase module3810. The item purchase module 3812 allows the user to place items in ashopping chart and purchase (or otherwise acquire) the items. The itempurchase module 3810, in turn, may include a buy rescind module 3814.The buy rescind module allows the user to rescind an item purchase inthe manner described more fully below. The item purchase module 3810 mayalso include a virtual account module 3816. As will be described ingreater detail below (in Section D), the virtual account module 3816allows the user to make item purchases after the user has purchased (orotherwise arranged to receive) a user device, but at this point in time,the user has not yet been assigned a particular user device.

The IRA functionality 3806 may include yet additional modules, asindicated by the label which reads, “Other Store Modules” 3818. Otherimplementations of the merchant store module 318 may omit one or moremodules shown in FIG. 38.

The merchant store module 318 may include a device interface module3820. The device interface module 3820 generally includes functionalitywhich allows the server-side merchant store 318 to interact with thedevice-side store interaction module 344. The device interface moduleincludes a markup presentation module 3822. The markup presentationmodule 3822 provides a series of pages (e.g., such as representativepage 3824) to the user device. The pages may be formulated in any markuplanguage or any other format. The device presentation interface module3820 may also include a device response processing module 3826. Thedevice response processing module 3826 receives responses from the userswho interact with the pages provided by the markup presentation module3822. For example, the users may select links in pages provided by themarkup presentation module 3822. The user's selections are conveyed backto device response processing module 3826 using the HTTP protocol orsome other protocol or combination of protocols.

FIGS. 39-41 show a representative collection of pages produced by themarkup presentation module 3822. FIG. 39 shows an introductory page3902, which the markup presentation module 3820 may display to the userwhen the user first accesses the merchant store module 318. Theintroductory page 3902 provides a portal which invites the user toexplore various browse categories, review recommended items, enter asearch, and so on. FIG. 40 shows a browse page 4002. The browse page4002 allows the user to browse for items using various subject-mattercategories. FIG. 41 shows an item detail presentation 4102, whichprovides information regarding a single eBook item that the user maypurchase through the item purchase module 3812. In the case in which theitem detail information cannot fit onto one page, the markuppresentation module 3820 may display this information in a series ofpages, as indicated in FIG. 40.

B.7.b. Illustrative Approach to Rescinding a Purchase

FIG. 42 shows a flowchart which depicts an illustrative procedure 4200for rescinding a purchase using the buy rescind module 3814 of FIG. 38.

In block 4202, the item purchase module 3812 receives the user'spurchase of an item. The user may make the purchase by making aselection which initiates a fulfillment operation.

In block 4204, the IPS 102 processes and potentially delivers thepurchased item to the user's device in the manner described above.

In block 4206, the buy rescind module 3814 presents an option to theuser which invites the user to rescind her purchase made in block 4302.In one case, the buy rescind module 3814 may present this option in a“thank you” page or the like, which is provided to the user followingthe purchase of the item. At this stage, as indicated by the prior block4204, the item purchase module 3812 is in the course of fulfilling theuser's purchase of the item.

In block 4208, it is assumed that the user does in fact activate the buyrescind option.

In block 4210 the buy rescind module 3814 rescinds the user's purchaseof the item, if possible.

B.8. Illustrative Content Manager Module and Media Library Module

The device-side content manager module 342 provides a tool that allowsthe user to review and manage items that are available for consumptionby the user device 104. FIG. 44 shows additional detail regarding thecontent manager 342. FIG. 44 also illustrates the manner in which thecontent manager 342 may interact with other modules, such as theserver-side personal media library module 324 and the subscriptionmodule 310.

The content manager module 342 includes a presentation module 4302. Thepresentation module 4302 shows various items available for the user toconsume using the user device 104. The items may originate from varioussources. A first source corresponds to the user device's internal devicememory 336. A second source corresponds to a portable memory module 4304that may be coupled to the user device 104, such as a flash card or thelike. A third source corresponds to items identified in the user'sserver-side personal media library module 324. More specifically, thecontent manager module 342 may receive information from the medialibrary module 324 regarding on-demand (“a la carte”) selections, suchas eBook items, specifically-selected newspaper and magazine issues, andso on. A fourth source corresponds to items identified in thesubscription module 310. More specifically, the content manager module342 may provide information regarding the user's subscriptions and thelatest issues associated with those subscriptions. In regards tosubscriptions, in one illustrative case, the content manager module 342may store the last n days for each of the user's subscriptions.

In one illustrative implementation, the content manager module 342 hasaccess to device-side metadata that identifies the items stored on thepersonal media library module 324 and/or the subscription module 310.This avoids the need for the user to make on-demand queries to theseserver-side modules to determine their contents.

According to another feature, the presentation module 4302 includes afiltering module 4306. The filtering module 4306 allows the user toselect a criterion (or criteria) for use in determining what types ofitems are displayed by the presentation module 4302. For instance, theuser may opt to restrict the presentation to only items stored in thedevice-side internal memory 336, and so on.

The content manager module 342 also includes an update processing module4308. The purpose of the update processing module 4308 is to update thedevice-side metadata that describes the contents of the personal medialibrary module 324. The update module 4308 may be invoked at varioustimes when the user device and IPS 102 interact with each other for anyreason. For example, the update module 4308 may be invoked as part ofthe collection of operations that are triggered by the receipt of a TPHsignal.

Referring now to the personal media library module 324, this module 324stores items that the user has previously purchased in a la cartefashion. More specifically, the personal media item library 324 maystore pointers 4308 which reference the items in the merchant contentstore 308 that the user has purchased. In the manner described above,the user may receive a previously-purchased item via the contentdelivery module 316, which, in turn, contacts may the personal medialibrary module 324 to verify that the user is indeed authorized toreceive the requested item. The user may decide to download an itemagain for any reason, such as in the case in which the content wasinadvertently deleted from the user's device local store(s).

The user may download subscription-related items in a similar manner.Namely, the content delivery module 316 accesses the subscription module324 to determine whether the user is authorized to download an issue orthe like. Permission information provided by the subscription module 324is performed on the level of subscriptions, rather than individualissues within a subscription.

FIG. 44 shows a content manager page 4402 provided by the presentationmodule 4302 of the content manager page 4402. This page 4402 showsvarious items that are available for the user to consume using the userdevice 104. The page 4402 also provides tags which indicate the sourceof the items, such as “Merchant” to indicate that the item is availablevia the personal media library module 324, “Device,” to indicate thatthe item is stored in the device-side memory 336, and “SD Card” toindicate that the item is stored on a removable memory module, and soon. Although not shown in FIG. 43, the content manager page 4402 mayprovide indicators which reveal whether an item is in the process ofbeing downloaded to the user device 104, and/or the item is undergoingother processing, etc.

FIG. 45 shows another content manager page that includes a filteringmenu 4502. The filtering menu 4502 is used by the filtering module 4304to control what types of items are displayed (corresponding to selectedsources, etc.), and in what order the items are displayed.

FIG. 46 shows another content manager page that shows another menu 4602.Among other functions, this menu 4602 allows the user to move items fromone source to another source, remove items, and so on.

FIG. 47 shows a procedure 4700 which illustrates how the user device 104and the IPS 102 share information.

In block 4702, one or more modules in the system 300 receive atriggering event. The triggering event signals that it is time forvarious housekeeping operations, such as the sharing of informationbetween the user device 104 and the IPS 102. One representativetriggering event may correspond to the sending of a TPH signal from theIPS 102 to the user device 104, which initiates a host of operations,including an information synchronization operation. Another triggeringevent may correspond to the powering up of the user device 104 or otherchange in state of the user device 104, and so forth.

In block 4702, one or more appropriate modules in the system 300 shareinformation which one or more other modules for the purpose ofsynchronization. To name one example, block 4702 may entail the userdevice 104 sending its annotations that a user has created for aparticular item to the IPS 102, for storage in a backup annotation store1116. Further, block 4702 may entail the personal media library module324 sending metadata down to the content manager module 342, where suchmetadata reflects the items that are referenced by the personal medialibrary module 324. Still other information-sharing operations may beperformed upon various triggering events.

In addition to the above periodic synchronization operations, the IPS102 can interact with the user device 104 to restore the contents of theuser device 104 when the stored content of the user device 104 is nolonger accessible, e.g., because the user has invoked a hard resetcommand, etc.

B.9. Illustrative Reader Module, Annotation Functionality, and AudioPlayer Module

Recall that the reader module 340, introduced in the context of FIG. 3,provides an interface that allows a user to read an eBook. FIG. 48 showsone page 4802 of text content produced by the reader module 340,corresponding to the novel Moby Dick, by Herman Melville. The user maychange the size of the font through an appropriate menu (not shown). Theuser may view his or her progress through the book via a progressdisplay 4804. The number of dots in the progress display, relative tothe total length of the display, reflects how far the user has advancedinto the book. Any page of readable content may include one or moreembedded links that may be activated. Note, for instance, button 4806 inpage 4802. In this case, the reading material being displayed by thereader module 340 corresponds to a sample of a more complete item, suchas a chapter of a book. The page 4802 includes a button 4806 thatinvites the user to select the full version of the item. In anotherimplementation, the button 4806 may invite the user to purchase anotherportion of the item (such as another chapter in a book, another issue ina magazine series, and so forth). In another case, a link may identifyan item that is related to the content being presently displayed basedon one or more matching considerations; for example, item recommendationmodule 3810 of FIG. 38 may identify a related item based on variousmatching considerations. Clicking on the button 4806 directs themerchant store module 318 to purchase (or otherwise acquire) andinitiate delivery of an identified item, e.g., in the illustrated case,a full version of content being read by the user in page 4802.

FIG. 49 shows a flowchart which depicts an illustrative procedure 4900for dynamically supplying item identification information when a useractivates a link in a page.

In block 4902, the user device 104 provides a presentation that includesa link, such as page 4802 that includes button 4806. The user device 104may use a template to display the page. The template may includeprovisions for presenting the link, but does not associate the link withany kind of code which uniquely identifies a particular item. In otherwords, the page includes a placeholder field in place of the actualcode.

More specifically, recall that, for certain types of items, the contentreception system 302 stores the items in the content store 308 withoutformally integrating identification information with these items. Whenthe content delivery module 316 delivers such an item to the user, itmay inject the identification information into the header of the item(using the metadata injection module 2316). But, at this stage, the linkinside the item still is not populated with identification information.

In block 4904, the user device 104 receives the user's selection of thelink.

In block 4906, the user device 104 or some other entity may dynamicallypopulate the link information so that it includes a uniqueidentification information (e.g., a unique number) associated with thelink. Consider the specific case in which, as indicated above, the page4802 displays a sample of an item, and the button 4806 allows the userto access the full version of the item. When the user clicks on thebutton 4806, the device 104 may populate the link associated with thebutton 4806 with identification information associated with the fullversion of the item. The identification information is provided to theuser device by the content delivery module 316, along with the sampleitem; for instance, the identification information may be conveyed inthe header of the sample item. The populated link may then be invoked toperform an action, such as by accessing the merchant store module 318 topurchase a full version of the item, which initiates delivery of thisitem to the user.

FIG. 50 shows an annotation menu 5002 that the user may invoke in thecourse of reading an eBook. The user may invoke the menu 5002 tohighlight a passage in the text, add a note associated with the text,and so on. The user may perform these operations using the cursor-movingmechanism 506 and/or using some other input mechanism(s). For instance,the user may demarcate a potion of a text to highlight by moving thecursor to corresponding beginning and ending locations in thesupplemental display part 504 (e.g., by rotating a cursor wheel, etc.)and then selecting those locations (e.g., by pressing down on the cursorwheel, etc.).

Continuing with the theme of annotations, as shown in FIG. 48, the usermay enter a bookmark by clicking next to a mark icon 4806 in the cornerof the page 4802. Further, FIG. 51 shows a way to identify locations inan eBook which have been marked by the user. Namely, FIG. 51 shows aprogress display. The small black triangles illustrate the location ofuser-created bookmarks within the text.

FIG. 52 shows various features associated with the audio player module410 (introduced in FIG. 4) and the environment in which the audio playermodule 410 may operate. There are at least two mechanisms that the userdevice 104 may use to receive audio items. In a first mechanism, theuser may use a personal computer 5202 or other type of data processingdevice to download an audio item from a source 5204 of audio items. Inthe first access mechanism, the personal computer 5202 may access theaudio source 5204 via a non-wireless connection, such as a conventionaltelephone or cable modem, a DSL connection, a T1 connection, and soforth. Upon receipt, the user may then transfer the audio item to theuser device 104 via a USB connection, portable memory module, or othertransfer mechanism. In a second mechanism, the same communicationinfrastructure 106 that is shown in FIG. 2 may be used to receive anaudio item from the audio source 5204 and then transfer this audio itemto the user device 104. In other words, the communication infrastructure106 transfers audio items in the same manner as eBook items and thelike, where the audio source 5204 functions as one of the contentsources 304 shown in FIG. 3. As explained, the communicationinfrastructure 106 may rely, at least in part, on wirelesscommunication.

The audio source 5204 may represent a commercial supplier of audio itemsor other type of organization that supplies audio items on a fee-basisor on a non-fee-basis (e.g., including libraries, governmentalorganizations, etc.). In this context, the audio source 5204 may beaccessible to the personal computer 5202 or other device as aWAN-accessible resource (e.g., as an Internet-accessible site or thelike). The audio source 5204 may also represent a user or a community ofusers that supply audio items for dissemination to other users.

Upon receipt, the audio player module 410 may store the audio item in abackground music file 5206 and/or an audio book file 5208. The audioplayer module 410 may be configured to play the audio items in thebackground music file 5206 as background music. For instance, the audioplayer module 410 may play an audio item in the background music file5206 when the user is reading a newspaper, searching the web, and so on.In one case, audio player module 410 may play the audio items in thebackground music file 5206 in a random order. The audio player module410 may provide controls that allow the user to access the backgroundmusic file 5206, pause the playing of background music, skip to a nextaudio item in the random playlist, and so on.

The audio player module 410 may be configured to allow a user tointeract with and consume audio items stored the audio books file 5208in generally the same manner as textual content. For example, page 5210shows one user interface page that allows a user to control the audioplayback of an audio book. The audio player module 410 allows the userto move within the content of an audio item using various forwardcommands, back commands, etc. Further, the audio player module 410stores the point in the audio item at which the user stopped listening;upon returning to the item at a later time, the audio player module 410begins playing from this point onward. Other modules of the user device410 may manage the audio item in the same banner as an eBook item. Forexample, the content manager module 342 may display metadata regardingan audio item in its list of available items (e.g., see the “Sun AlsoRises” entry in FIG. 44).

B.10. Illustrative Web Browsing Functionality

FIG. 53 presents a simplified depiction of the system 200 of FIG. 2. Inthis simplified depiction, the device-side browser module 402 interactswith the item-providing system (IPS) 102 via a network 212, such as theInternet. The IPS 102 includes a browsing proxy module 326. The browsermodule 402 is first directed to the browsing proxy module 326 when itattempts to access one of the network-accessible resources 226. In thisillustrative and representative manner, the device browser module isprecluded from directly accessing the network-accessible resources (asindicated by the X mark shown in FIG. 53). It should be noted that thebrowser module 402 is only one way that the user device communicateswith the IPS 102. The use of the browsing proxy module 326 does notaffect other communication routes, such as the transfer protocol betweenthe item delivery system 312 and the to-do list processing module, aswell as the interaction between the merchant store module 318 and thedevice-side store interaction module 344.

The IPS 102 may establish different business rules to govern the user'saccess to “external” network-accessible resources. In one case, the IPSmay discriminate between a first class of non-fee resources 5302 forwhich it does not charge a fee (or charges a relatively smaller fee),and a second class of fee resources 5304 for which it charges a fee (orcharges a relatively larger fee).

FIG. 54 shows a procedure 5400 which represents one illustrative way ofgoverning access to network-accessible resources using the browsingproxy module 326.

In block 5402, the browsing proxy module 326 receives a user's requestto connect to a network-accessible resource, such as a website or thelike.

In block 5404, the browsing proxy module 326 determines whether the sitethat the user wishes to connect to corresponds to the services providedby the IPS 102 itself If this is the case, then, in block 5406, thebrowsing proxy module 326 grants the user access to the requestedresources.

If block 5404 is answered in the negative (meaning that the user is notattempt to gain access to the IPS 102 itself), the flow advances toblock 5408, where the browsing proxy module 326 determines whether theuser is attempting to gain access to one or more of the designed non-fee(or reduced fee) resources 5302. If this is the case, then, in block5406, the browsing proxy module 326 grants the user access the requestedresources (in block 5406).

If block 5408 is answered in the negative (meaning that the user is notattempt to gain access to the IPS 102 or a free resource 5302), the flowadvances to block 5410, where the browsing proxy module 326 determineswhether the user is attempting to gain access to one or more of thedesignated fee resources 5304. If this is the case, then, in block 5412,the browsing proxy module 326 next determines whether the user has paidor has agreed to pay the required fee. If this block 5412 is answered inthe affirmative, the browsing proxy module 326 assesses appropriate fees(in block 5414) and then grants the user access the requested resources(in block 5406). In one case, the system 300 may be set up so that theuser may pay a fee for each item that the user wishes to access, e.g.,on a per-access basis. In another case, the system 300 may be set up sothat the user may pay a fee to access any number of items for apredetermined amount of time (such as a day, week, etc.). In any case,the user may be given the option of automatically acceptingaccess-related fees when the user makes an access attempt, e.g., withoutquerying the user each time he or she wishes to access an item.

If none of the conditions set forth above is satisfied, then, in block5416, the browsing proxy module 326 denies the user access to therequested resource.

FIG. 55 illustrates a bookmark page 5502 (also known as a favoritespage) that may be provided by the device browser module 402. The page5502 includes a list of links. The user may click on any link to connectto a corresponding network accessible resource.

FIG. 56 shows a menu 5602 that the device browser module 402 may use toenter network addresses, such as URLs, using the user device 104.

C. Illustrative Administrative-Related Functionality

C.1. Overview of Functionality

This section provides information regarding various administrative orbackend tasks that may be performed using the system set forth inSections A and B. One administrative function pertains to monitoring theperformance of various aspects of the system. Another administrativefunction pertains to testing the operation of the system. Anotheradministrative function pertains to diagnosing problems or other issuesthat may be present in the system. Another administrative functionpertains to upgrading the instruction-bearing content (e.g., software)used by the user device 104. The above-described functions mayintersect. For example, the testing and diagnosing functions may rely onthe performance-monitoring function. The upgrade-related function mayrely on the testing and diagnosing functions to determine whether aninstruction upgrade is appropriate.

FIG. 57 provides a simplified depiction of the system 200 introduced inFIG. 2. This system 200 is used as a vehicle to explain the variousadministrative functions described above. However, the administrativefunctions described here may also be implemented using other types ofsystems.

The system 200 allows an item-providing system (IPS) 202 to interactwith a user device 104 via communication infrastructure. Thecommunication infrastructure includes a wireless provider system 202 anda communication-enabling system 208. The communication-enabling system208 interacts with the IPS 102 via a network 212, such as a wide areanetwork (WAN), and, more particularly, the Internet.

The system 200 implements the various administrative functions describedabove at various levels, as will be described below.

C.2. Illustrative Performance Monitoring, Testing, and DiagnosingFunctionality

FIG. 57 illustrates that various parts of the system 200 may monitor theperformance of the system 200, from respective “vantage points.” Forinstance, the user device may include a device-side performance loggingmodule 5702 for recording various events associated with the performanceof the system 200, with respect to performance issues that are visibleto the user device 104. The device-side performance logging module 5702may store performance information in a performance log 416 (introducedin the context of FIG. 4).

The wireless provider system 202 may likewise include a performancelogging module 5704 for recording various events associated with theperformance of the system 200, with respect to performance issues thatare visible to the wireless provider system 202. The performance loggingmodule 5704 may store performance information in a performance log 5706.

The communication-enabling system 208 may likewise include a performancelogging module 5708 for recording various events associated with theperformance of the system 200, with respect to performance issues thatare visible to the communication-enabling system 208. The performancelogging module 5708 may store performance information in a performancelog 5710.

The IPS 102 may include a customer service module 5712 for performingvarious functions. As a first function, the IPS 102 may alsoindependently record various events and store such events in an IPS-sideperformance log 5714. Further, the customer service module 5712 mayobtain any of the performance information collected by the user device104, the wireless provider system 202, and/or the communication-enablingsystem 208. In one particular case, the customer service module 5712automatically collects performance information from different parts ofthe system 200. In another case, the customer server module 5712 maymake on-demand targeted inquires into different aspects of the system200, querying the performance information collected by the user device104, wireless provider system 202, and/or the communication enablingsystem 208. For instance, a user may call a customer servicerepresentative to identify a problem with receiving a download in aparticular region of a country. The customer service representative mayexamine the performance information provided by any part of the systemto help uncover the source of the problem.

In addition, an administrator at the IPS 102 may proactively testvarious parts of the system 200. For instance, the IPS 102 may include aserver-side testing module 5716. The server-side testing module 5716 maybe used to periodically send test signals to a set of test user devices,requesting the test user device to respond. Or the testing module 5716may send the testing signals to the test user devices in an on-demandmanner. A test user device may include a complementary test module 5718for receiving and responding to such a test signal. (Note that,collectively, the device-side performance logging module 5702 and thedevice-side testing module 5718 correspond to the monitoring and testingfunctionality 414 introduced in FIG. 4.) The server-side testing module5716 may monitor the response(s) it receives from each test user device,including whether a response was received at all, and/or variousperformance metrics associated with response, and so forth. Theserver-side testing module 5716 and/or a human administrator may reviewthe results to help diagnose performance issues within the system 200.

FIG. 58 shows a procedure 5802 which formalizes the operation of thetesting modules (5716, 414) in flowchart form.

In block 5802, the server-side test module 5716 may determine whether itis time to test the system 200.

In block 5804, if it is time to test, the server-side testing module5804 may send test probes to one or more test devices.

In block 5806, the server-side testing module 5806 may identify whetherit has received a response from the test user devices, and if so, thenature of the response.

C.3. Illustrative Upgrade-Related Functionality

Returning to FIG. 57, this figure illustrates that the IPS 102 includesa server-side upgrade module 5720. The user device 104 includes acomplementary device-side upgrade module 418 (which was introduced inthe context of FIG. 4). By way of overview, in one case, server-sideupgrade module 5720 may be manually operated to push an upgrade or otherinformation down to the user device 104, whereupon the device-sideupgrade module 418 loads the identified upgrade or other information inan appropriate manner. In a second case, the server-side upgrade module5720 may automatically receive version information from the user device(supplied by the device-side upgrade module 418). The server-sideupgrade module 5720 may compare the received version information withthe current version of the software. The server-side upgrade module 5720may then initiate any upgrades that may be appropriate, e.g., bydownloading a patch or a full version of the desired instruction-bearingitem to bring the user device up-to-date.

FIG. 59 shows a procedure 5900 which depicts a manual mode of providingupdates to the user device 104.

In block 5902, an administrator associated with the IPS 102 identifiesan upgrade to be made to the user device 104.

In block 5904, the server-side upgrade module 5720 may send the upgradedown to the user device, whereupon the device-side upgrade module 418incorporates the upgrade into its body of instructions. The updatingoperation is transparent in the sense that the end-user is optionallynot asked to participate in the updating operation, and may not be awareof the updating operation.

FIG. 60 shows a procedure 6000 which depicts an automated mode ofproviding updates to the user device 104.

In block 6002, the server-side upgrade module 5720 may receiveinformation regarding a current version of instructions that is beingused by a user device.

In operation 6604, the server-side upgrade module 5720 may compare thedevice's version with the current versions of the instructions.

In operation 6606, the server-side upgrade module 5720 may automaticallyprepare an upgrade for use by the user device, e.g., by computing adelta file that expresses the difference between the current version ofthe instructions and the device's version of the instructions. Theupgrade module 5720 may transfer the upgrade to the user device 104either as a patch or as a full file. The device-side upgrade module 418receives the upgrade and takes action to incorporate the upgrade. Again,the updating operation is transparent in the sense that the end-user isnot asked to participate in the updating operation, and may not be awareof the updating operation.

FIG. 61 shows an exemplary communication package used by the system 200to transfer updates of any type to the user device 104. The packageincludes a header 6102 and a body 6104. The header 6102 may includefields that convey version information, attribute information, checksuminformation, and so forth. The body 6104 may include a manifest, and/orinstruction-bearing content (script content, program content, etc.),and/or media content, and/or other type of content. The body may beexpressed as a tar file or by using some other format or combination offormats. The information expressed by the package may be scrambledtogether with random information to help prevent non-authorizedindividuals from accessing the information.

The package serves as a general-purpose container for communicating anytype of information to the user device 104 to elicit any type ofbehavior from the user device 104. In one case, an administrator may usethe package shown in FIG. 61 to download an instruction-bearing item toa user device 104. The device 104 responds by loading this item into itsmemory; the device 104 thereafter operates based on the programinstructions provided in the item.

In another case, the administrator may use the package shown in FIG. 61to download other types of content to the user device 104, such as anykind of message content that is displayed by the user device 104. Forinstance, the downloaded content may pertain to a message that the userdevice 104 is instructed to display in a power-off mode (e.g., in thecase that the user device uses non-volatile display technology that maypresent information on a display in a power-off mode of operation). Toprovide this message, the package may include a bit map which providesthe desired message and optionally script content which directs the userdevice 104 how to display the message. Other applications are possible.

D. Illustrative Provisioning Functionality

D.1. Overview of Provisioning Functionality

FIG. 62 shows a system 6200 for provisioning new user devices. Morespecifically, the system 6200 includes provisioning functionality 6202that interacts with a newly manufactured user device 6204 (or componentthereof), e.g., at a factory or like environment. The new user device6204 may include a provisioning module 6206. The device-sideprovisioning module 6206 receives temporary contact information 6208from the provisioning functionality 6202, which may include one or moreidentification numbers. The provisioning functionality 6202 may alsointeract with communication infrastructure 6210 to provide thecommunication infrastructure 6210 with provisioning information 6212.The provisioning information 6212 relates to the temporary contactinformation 6208 stored by the user device 6204.

As illustrated in FIG. 62, the user device 6206 may use the temporarycontact information 6208 to establish a first access to thecommunication infrastructure 6210. The communication infrastructure 6210may then forward more permanent contact information 6214 to the userdevice 6204. The user device 6204 may thereafter uses the more permanentcontact information 6214 to access the IPS 102 and othernetwork-accessible resources. The provisioning approach allows the userto use the user device 6204 without performing complex and burdensomeconfiguration operations.

Addition details regarding one illustrative manner of provisioning userdevices is described in U.S. Ser. No. 11/277,876, filed on Mar. 29,2006, entitled “Over-the-air Device Provisioning and Activation,” namingthe inventors of Subram Narasimhan, et al.

D.2. Illustrative Virtual Account Processing

FIG. 63 illustrates a procedure 6300 for allowing a user to purchaseitems (or more generally, acquire items) immediately after the userpurchases a user device 104. This procedure 6300 may be performed atleast in part by the virtual account module 3816 of FIG. 38.

In block 6302, a purchasing system receives the user's purchase of a newuser device.

In block 6304, the purchasing system or some other module may establisha virtual account for the user. The virtual account is establishedbefore a user device is even assigned to the user.

In block 6306, the purchasing system receives one or more item purchasesmade the user. The purchasing system associates these purchases with thevirtual account created in block 6304.

In block 6308, when a user device is assigned to the user, thepurchasing system or some other module may associate the virtual accountwith the assigned user device. This linking operation allows the user touse his or her new user device to receive and consume the items thatwere applied to the virtual account.

D.3. Illustrative Initial Testing

FIG. 64 shows an approach to testing a new user device 6402, referredto, in this context, as a device under test (DUT). For instance, theapproach may be used to test the device in a factory or in some otherstage of production.

By way of introduction, the user device 6402 may include a preferredroaming list (PRL) 6404 and a most recent used (MRU) table 6406. The PRL6404 includes a list of target frequencies that that the user device mayinvestigate in order to establish communication with a communicationstation or the like. The MRU table 6406 identifies the frequency thatthe user device 104 most recently used to gain access to a communicationstation.

FIG. 64 also shows test equipment 6408. The test equipment 6408 is used,in part, to test the ability of the user device 6402 to establishcommunication with a communication station. The test equipment 6408 mayuse a test channel 6410 to establish communication with the user device6402 for the purpose of performing a test.

To expedite the testing, the approach illustrated in FIG. 64 programsthe MRU table of the user device 6406 so that it stores information thatidentifies the test channel 6410 of the test equipment 6408. This allowsthe user device 6402 to quickly establish contact with the testequipment 6408, that is, by avoiding the need for the user device 6402to hunt for a frequency with which to communicate with the testequipment 6408.

As a further feature, the testing approach does not require storing atest PRL in the PRL table, and then, after the test, replacing the testPRL 6404 with an actual PRL 6404 to be used in the field. That is, inthe present approach, the PRL 6404 may maintain an actual PRLinformation throughout the testing operation.

FIG. 65 shows a procedure 6500 for implementing the above-describedtesting approach.

In block 6502, the MRU table 6406 stores information which identifiesthe test channel 6410 of the test equipment 6408.

In block 6504, the user device 6402 and the test equipment 6408 performthe test. In conducting the test, the user device 6402 does need to huntfor the channel of the test equipment 6408 because the appropriateaccess information is already stored it its MRU table 6406.

In closing, although the invention has been described in languagespecific to structural features and/or methodological acts, it is to beunderstood that the invention defined in the appended claims is notnecessarily limited to the specific features or acts described. Rather,the specific features and acts are disclosed as exemplary forms ofimplementing the claimed invention.

What is claimed is:
 1. An item-providing system to provide items forconsumption by a user operating a user device, the item-providing systemcomprising: an item delivery system coupled to the user device bycommunication infrastructure that uses, at least in part, wirelesscommunication, the item delivery system configured to: provide items forconsumption by a user operating a user device, wherein the item deliverysystem is coupled to the user device by communication infrastructurethat uses, at least in part, wireless communication, send a notificationmessage to the user device to notify the user device to access a listaccessible to the item-providing system, the list identifying at leastone instruction for the user device to perform; receive a request fromthe user device at least partly responsive to the notification messageusing a data-type channel, wherein the request is to forward the atleast one instruction to the user device; forward the at least oneinstruction to the user device using the data-type channel at leastpartly in response to the request; and receive an instruction from theuser device to remove one or more entries from the list, the one or moreentries of the list corresponding to the at least one instructionforwarded to the user device.
 2. The system of claim 1, wherein thenotification message is a telephone ring.
 3. The system of claim 1,wherein the at least one instruction corresponds to downloading an item,wherein the item-delivery system is configured to deliver the item tothe user device using the data-type channel.
 4. The system of claim 3,wherein the user device is an electronic book reader-type device, andwherein the item is consumable using the electronic book reader-typedevice.
 5. A method for interacting with a user device, using, at leastin part, wireless communication, comprising: sending a notificationmessage to the user device to notify the user device to access a listaccessible to an item-providing system, the list identifying at leastone instruction for the user device to perform; receiving a request fromthe user device at least partly responsive to the notification messageusing a data-type channel, wherein the request is to forward the atleast one instruction to the user device; forwarding the at least oneinstruction to the user device using the data-type channel at leastpartly in response to the request; and receiving an instruction from theuser device to remove one or more entries from the list, the one or moreentries of the list corresponding to the at least one instructionforwarded to the user device.
 6. The method of claim 5, wherein thenotification message is a telephone ring.
 7. The method of claim 5,wherein the at least one instruction corresponds to downloading an item.8. The method of claim 7, further comprising delivering the item to theuser device using the data-type channel.
 9. The method of claim 8,wherein the user device is an electronic book reader-type device, andwherein the item is consumable using the electronic book reader-typedevice.
 10. One or more non-transitory machine-readable media containingmachine-readable instructions for implementing: the method of claim 5.11. One or more computing devices, comprising: one or more processors;and memory to store computer-executable instructions that, when executedby the one or more processors, perform the method of claim
 5. 12. A userdevice for receiving items from an item-providing system for consumptionby a user operating the user device, comprising: a device processingmodule coupled to the item-providing system by communicationinfrastructure that uses, at least in part, wireless communication, thedevice processing module configured to: receive a notification messagesent by the item-providing system, the notification message notifyingthe user device to access a list identifying at least one instructionfor the user device to perform; send a request to the item providingsystem at least partly responsive to the notification message using adata-type channel, wherein the request is to forward the at least oneinstruction to the user device; receive the at least one instructionfrom the item providing system via the data-type channel at least partlyin response to the request; and send an instruction to theitem-providing system to remove one or more entries from the list, theone or more entries of the list corresponding to the at least oneinstruction received from the item-providing system.
 13. The user deviceof claim 12, wherein the notification message is a telephone ring. 14.The user device of claim 13, wherein the user device is configured torespond to the telephone ring without answering the telephone ring andwithout incurring an associated fee.
 15. The user device of claim 12,wherein the user device includes a power management module, wherein thepower management module is configured to transition from a first powerstate to a second power state in response to the receipt of thenotification message, wherein the first power state consumes less powerthan the second power state.
 16. The user device of claim 12, whereinthe at least one instruction corresponds to downloading an item.
 17. Theuser device of claim 16, wherein the device processing module isconfigured to download the item using the data-type channel.
 18. Amethod, performed by a user device, for interacting with anitem-providing system, using, at least in part, wireless communication,comprising: receiving a notification message from the item-providingsystem, wherein the item-providing system sends the notification messageto notify the user device to access a list identifying at least oneinstruction for the user device to perform; sending a request to theitem-providing system at least partly responsive to the notificationmessage using a data-type channel, wherein the request is to forward theat least one instruction to the user device; receiving the at least oneinstruction from the item-providing system via the data-type channel atleast partly in response to the request; and sending an instruction tothe item-providing system to remove one or more entries from the list,the one or more entries of the list corresponding to the at least oneinstruction received from the item-providing system.
 19. One or morenon-transitory machine-readable media containing machine-readableinstructions for implementing the method of claim
 18. 20. One or morecomputing devices, comprising: one or more processors; and memory tostore computer-executable instructions that, when executed by the one ormore processors, perform the method of claim
 18. 21. An item-providingsystem to provide items for consumption by a user operating anelectronic book reader-type device, the item-providing systemcomprising: a content reception system configured to receive electronicbooks from one or more content sources and store the electronic books ina content store; a merchant store module configured to add an entry to alist associated with the electronic book reader-type device, wherein thelist includes a plurality of entries and the entry includes aninstruction for the electronic book reader-type device to download anelectronic book purchased by the user and stored in the content store;and an item delivery system coupled to the electronic book reader-typedevice by communication infrastructure that uses, at least in part,wireless communication, the item delivery system configured to: send anotification message to the electronic book reader-type device to notifythe electronic book reader-type device to access the list associatedwith the electronic book reader-type device at least partly in responseto the user of the electronic reader-type device purchasing theelectronic book; generate an index for the electronic book, the indexlinking component parts of the electronic book to respective locationsof the component parts in the electronic book; and provide informationto the electronic book reader-type device indicating whether or not theindex is available for download.
 22. An electronic book reader-typedevice for receiving items from an item-providing system, the electronicbook reader-type device comprising: a store interaction moduleconfigured to purchase an electronic book from the item-providingsystem; a device processing module coupled to the item-providing systemby communication infrastructure that uses, at least in part, wirelesscommunication, and the device processing module is configured to:receive a notification message sent by the item-providing system, thenotification message notifying the electronic book reader-type device totransition to a prescribed power state and to access a list associatedwith the electronic book reader-type device; send a request at leastpartly in response to the notification message to obtain an instructionfrom an entry of the list to download the electronic book from theitem-providing system; receive an instruction from the item providingsystem to download the electronic book; send, at least partly inresponse to receiving the instruction to download the electronic book, arequest to the item providing system to download the electronic book;and receive the electronic book and information from the item providingsystem, the information indicating whether or not the item providingsystem stores an index corresponding to the electronic book, whether ornot the item providing system stores one or more annotations for theelectronic book, or both.
 23. A method for providing an entry to a userdevice, comprising: maintaining, by an item-providing system, a queueassociated with a the user device, the queue including a list of entriesthat includes one of more first instructions for the user device toperform one or more actions; determining, by the item-providing system,a schedule according to which to send a notification message; initiatingcommunication with the user device by sending, to the user deviceaccording to the schedule, the notification message to notify the userdevice that a new entry is added to the list of entries; receiving, fromthe user device and at least partly in response to the notificationmessage, a request to forward the list of entries to the user device;and forwarding the list of entries to the user device at least partly inresponse to the request.
 24. The method of claim 23, wherein anopportunity to send the notification message occurs at predeterminedtimes, wherein the determining the schedule ascertains whether apredetermined time of the predetermined times has arrived.
 25. Themethod of claim 23, wherein at least one part of a day is favored overat least one other part of the day to send a notification message,wherein the determining the schedule ascertains whether a preferred partof the day has arrived.
 26. The method of claim 23, wherein thedetermining the schedule is based on an amount of time that has elapsedsince sending a prior notification message.
 27. The method of claim 23,wherein the determining the schedule is based on a number ofnotification messages that have been sent in a recent span of time. 28.The method of claim 23, wherein the determining the schedule is based onan amount of time that the new entry has been added to the first listwithout having sent a notification message.
 29. The method of claim 23,wherein the determining the schedule is based on a consideration of acost associated with sending the notification message.
 30. The method ofclaim 23, wherein the determining the schedule is based on aconsideration of a number of notification messages in the first list.31. The method of claim 23, wherein the notification message isassociated with an instruction to download an identified item.
 32. Themethod of claim 31, wherein the determining the schedule is based on anassigned priority associated with the identified item.
 33. The method ofclaim 31, wherein the determining the schedule is based on a type ofitem associated with the identified item.
 34. The method of claim 31,wherein the determining the schedule is based on a consideration ofwhether a user of the user device expressly selected the identified itemor whether the identified item was added to the list based on anautomated routine.
 35. The method of claim 31, wherein the determiningthe schedule is based on a size of the identified item.
 36. The methodof claim 23, wherein the determining the schedule is based on aconsideration of how recently a user of the user device made an actionthat prompted the new entry to be added to the list.
 37. The method ofclaim 23, further comprising ascertaining prior behavior of a user whooperates the user device, wherein the determining the schedule is basedon the prior behavior of the user.
 38. The method of claim 23, furthercomprising ascertaining a power-related state of the user device,wherein the determining the schedule is based on the power-relatedstate.
 39. One or more non-transitory machine-readable media containingmachine-readable instructions for implementing the method of claim 23.40. One or more computing devices, comprising: one or more processors;and memory to store computer-executable instructions that, when executedby the one or more processors, perform the method of claim
 23. 41. Amethod for providing an item to a user device, comprising: identifyingan event that initiates a process of downloading an item to a userdevice; determining, at least partly in response to identifying theevent, a status of an entry including an instruction to download theitem, wherein the entry is included in a list of entries associated withthe user device; sending, to the user device, a notification messagewhen the status of the entry indicates that the instruction to downloadthe item is ready to be sent to the user device, the notificationmessage notifying the user device to access the entry of the list ofentries associated with the user device; receiving, from the user deviceand at least partly in response to the notification message, a requestto forward the list of entries to the user device; and forwarding, tothe user device and at least partly in response to the request, the listof entries.
 42. One or more non-transitory machine-readable mediacontaining machine-readable instructions for implementing the method ofclaim
 41. 43. One or more computing devices, comprising: one or moreprocessors; and memory to store computer-executable instructions that,when executed by the one or more processors, perform the method of claim41.
 44. An item-providing system, comprising: a list server moduleconfigured to: maintain a first list of entries for a first user deviceand a second list of entries for a second user device, the first list ofentries including at least one entry that includes an instruction thatis different from an instruction of at least one entry of the secondlist of entries; send a notification message to the user device tonotify the first user device that a new entry is added to the list ofentries; receive a request by the first user device, at least partly inresponse to the notification message, to access at least one part of thefirst list of entries, wherein each entry in the at least one partprovides an instruction for the first user device to perform anidentified action; provide the at least one part of the first list tothe first user device at least partly in response to the request; andscheduling functionality configured to determine a timing at which tosend the notification message.